feat(srg): Removes MaxItems, and API errors in the resource keep violation paths#988
Merged
d0weinberger merged 1 commit intomainfrom Feb 19, 2026
Merged
feat(srg): Removes MaxItems, and API errors in the resource keep violation paths#988d0weinberger merged 1 commit intomainfrom
MaxItems, and API errors in the resource keep violation paths#988d0weinberger merged 1 commit intomainfrom
Conversation
MaxItems, and API errors in the resource keep violation paths
Kirdock
approved these changes
Feb 19, 2026
tomazpu
approved these changes
Feb 19, 2026
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
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.
Why this PR?
We want the API to validate the number of links.
What has changed?
MaxItems: 5is removed again from the links collection and API errors will contain the violation path, i.e. the path in the JSON payload which violates constraints.How does it do it?
Example:

How is it tested?
E2E tests are in place and work
How does it affect users?
They will see a better error message, but it will not appear in
plan, only inapply.Issue: CA-17812