improvement(TokenResource)!: rename generated created_at attribute to inserted_at.
#430
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…to `inserted_at`.
If you are using the token resource this is a **breaking change**. You will need
to generate new migrations using:
mix ash_postgres.generate_migrations --name=rename_created_at_to_inserted_at
It will ask you if you are renaming `created_at` to `inserted_at` - answer yes.
|
Thoughts @zachdaniel? Not sure if it's worth the major release just to change the name of an attribute. |
|
IMO it is definitely not worth it. We can make it configurable if some people need that. |
|
👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If you are using the token resource this is a breaking change. You will need to generate new migrations using:
It will ask you if you are renaming
created_attoinserted_at- answer yes.This updates and closes #85.