Add number-aware underscore naming strategy #1059
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
alcaeus
force-pushed
the
add-underscore-number-aware-naming-strategy
branch
from
6ed4932
to
10e5336
Compare
|
I suggest marking the |
|
@stof I was going to wait for people to upgrade to ORM 2.7 before doing that: the naming strategy change is a BC break, so the current underscore naming strategy shouldn't be deprecated if a user is still using ORM 2.6. |
|
@ro0NL thanks for the reminder! New recipes for 1.12 and 2.0 are coming to make use of simplified cache configuration! |
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.
Fixes #1057: introduces a new naming strategy that avoids the deprecation notice when using a number-unaware underscore naming strategy.