CLOUDP-304930: IPA-102 pattern test #498
Merged
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
wtrocki
force-pushed
the
CLOUDP-304930
branch
2 times, most recently
from
cb4aa3f to
de94c1d
Compare
marcosuma
approved these changes
Mar 11, 2025
lovisaberggren
approved these changes
Mar 11, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
This PR implements two rules from the IPA-102 specification to enforce proper resource identifier formatting in API paths:
Collection Identifier Pattern Rule (xgen-IPA-102-collection-identifier-pattern):
Ensures resource identifiers begin with a lowercase letter
Only allows ASCII letters and numbers in resource identifiers
Validates against the pattern /^[a-z][a-zA-Z0-9]*$/
Collection Identifier camelCase Rule (xgen-IPA-102-collection-identifier-camelCase):
The implementation includes comprehensive unit tests that cover valid patterns, invalid patterns, and exception handling scenarios.
Edit: moved other implementation to separate PR