Skip to content
New issue

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

[FEATURE-REQUEST] Configurable ID field #201

Open
leifg opened this issue Feb 24, 2021 · 2 comments
Open

[FEATURE-REQUEST] Configurable ID field #201

leifg opened this issue Feb 24, 2021 · 2 comments
Assignees
Labels
enhancement New feature or request planned

Comments

@leifg
Copy link

leifg commented Feb 24, 2021

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:

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.

@leifg leifg added the enhancement New feature or request label Feb 24, 2021
@tadasajon
Copy link

I also use schema's that don't have an id field

@christhekeele
Copy link

This would be nice to have. A better generic default might be to reflect on the schema's @primary_key field, as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request planned
Projects
None yet
Development

No branches or pull requests

4 participants