You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 3, 2024. It is now read-only.
If there has been a single field, then I would have used id_name and id_field to get the resource, but a single field is not defining the resource, I need 2 fields to define it uniquely. How can I do that?
for example:
a user is defined uniquely by fieldA and fieldB, conn.path_params will give those parameters, and we will need to use Repo.get_by on those field combined. As of now, there is no way to define 2 fields simultaneously
The text was updated successfully, but these errors were encountered:
👋 Hey! I'm sorry for the lack of movement on this. I shouldn't have left this for so long without a reply.
I am not currently writing Elixir at all, and therefore, I think it would be irresponsible of me to review PRs on this project. I just kept putting off reviewing the issues/PRs on this repo until I started writing Elixir again, but never got around to it.
That is my mistake, and I'm really sorry about that 🙏. You put in the time to make this issue, and you deserve a response at the very least.
I've marked the project as "not being actively maintained" in the readme. Please feel free to fork it with a different name and put it up on hex with current fixes.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If there has been a single field, then I would have used id_name and id_field to get the resource, but a single field is not defining the resource, I need 2 fields to define it uniquely. How can I do that?
for example:
a user is defined uniquely by fieldA and fieldB, conn.path_params will give those parameters, and we will need to use Repo.get_by on those field combined. As of now, there is no way to define 2 fields simultaneously
The text was updated successfully, but these errors were encountered: