feat(guidelines): avoid digits in camelCase #99
+76
−5
Conversation
This file contains hidden or 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
cgebken
requested changes
Sep 19, 2025
Contributor
cgebken
left a comment
cgebken
left a comment
There was a problem hiding this comment.
Just some minor suggestions :) Great ADR!
api-guidelines/global/json/naming-conventions/rules/should-use-camel-case-for-property-names.md
Outdated
Show resolved
Hide resolved
api-guidelines/global/json/naming-conventions/rules/should-use-camel-case-for-property-names.md
Show resolved
Hide resolved
...uidelines/rest/resources/naming-conventions/rules/must-use-camelcase-for-query-parameters.md
Outdated
Show resolved
Hide resolved
...uidelines/rest/resources/naming-conventions/rules/must-use-camelcase-for-query-parameters.md
Show resolved
Hide resolved
cgebken
changed the title
…-camel-case-for-property-names.md Co-authored-by: Christina Framke <[email protected]>
Co-authored-by: Christina Framke <[email protected]>
…e-camelcase-for-query-parameters.md Co-authored-by: Christina Framke <[email protected]>
Contributor
Author
|
Feedback from the Async API Community: In general we agree on avoiding digits in camelCase. But we also thought about common abbreviations like B2B, B2C, and E2E, which are also used in our marketplace ecosystem. As we change the rule to “avoid digits” and not "disallow digits", this should be fine for such special cases. We should disallow leading digits in property names, as this could lead to compile errors in common programming languages like Java. |
kiriakos
reviewed
Oct 21, 2025
Co-authored-by: Kiriakos Krastillis <[email protected]>
Contributor
|
LGTM, after adding more examples for DOs and DON'Ts |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Changelog:
Update