Add Rails/ValidateUniquenessCase #20
Merged
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
Bhacaz
force-pushed
the
validate_uniqueness_case
branch
from
0f00603 to
13d8e47
Compare
Bhacaz
force-pushed
the
validate_uniqueness_case
branch
from
13d8e47 to
1d82946
Compare
ericproulx
approved these changes
Apr 15, 2022
…-petal into validate_uniqueness_case
ericproulx
approved these changes
Apr 25, 2022
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.
Entre Rails 6.0 et 6.1 le default de case_sensitive change. https://guides.rubyonrails.org/6_1_release_notes.html#active-record-notable-changes
L'idée est de faire un auto correct sur master, et remplacer les false pour des true pour avoir le même comportement. Mais les future (le temps d'arriver vers 6.1) va avoir un auto correct avec false.