We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the problem you're proposing to solve
I have a couple of schemas that don't have the field id. Judging by looking at the templates it seems like this is not configurable.
id
Describe the solution you'd like
It would be great to configure the name of the id columns somewhere in the resources.
Describe alternatives you've considered
For now I can get by by aliasing the Ecto column like this:
field :id, :string, source: :uuid
I might consider just renaming my ID field, so it's not a high priority ticket.
Additional context Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
I also use schema's that don't have an id field
Sorry, something went wrong.
This would be nice to have. A better generic default might be to reflect on the schema's @primary_key field, as well.
@primary_key
aesmail
No branches or pull requests
Describe the problem you're proposing to solve
I have a couple of schemas that don't have the field
id
. Judging by looking at the templates it seems like this is not configurable.Describe the solution you'd like
It would be great to configure the name of the id columns somewhere in the resources.
Describe alternatives you've considered
For now I can get by by aliasing the Ecto column like this:
I might consider just renaming my ID field, so it's not a high priority ticket.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: