feat(0043-standardise-restricted-value-casing.md) - create new adr #108
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
|
Hi Louis, I feel the same itch. Absolutely see the value of having a consistent coding/naming convention as it will benefit implementors. Not sure how much backwards incompatibility it's worth however. Might be good to bring the proposal to the working group. |
|
I get what you're saying but from my perspective if there's a time to fix this, it's 3.0, there's already some large changes coming that implementors are going to need to handle for, and this can set things up for future ease and success. Let me know if you'd like me to make a case to the WG. |
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.
Adding a new ADR to standardise various restricted value data types in order to ease implementation difficulty.