[BAE-171] Clarify maxItems, minItems, and uniqueItems errors#263
[BAE-171] Clarify maxItems, minItems, and uniqueItems errors#263dmiller113 wants to merge 2 commits intomainfrom
maxItems, minItems, and uniqueItems errors#263Conversation
|
To enable Rovo Dev code reviews, link your GitHub account to your Atlassian account. This is a one-time task that takes less than a minute. Once your account is linked, resubmit the pull request to trigger a code review. |
π¦ Changeset detectedLatest commit: 804a81f The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Codecov Reportβ
All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #263 +/- ##
==========================================
+ Coverage 68.80% 70.07% +1.26%
==========================================
Files 19 20 +1
Lines 638 665 +27
Branches 117 125 +8
==========================================
+ Hits 439 466 +27
Misses 195 195
Partials 4 4 β View full report in Codecov by Sentry. π New features to boost your workflow:
|
maxItems, minItems, and uniqueItems errorsmaxItems, minItems, and uniqueItems errors
Context
Previously, those three errors for keywords attributed to the array itself and not items inside it produced messages that incorporated their keyword resulting in confusing error messages such as
/foo: MINITEM must not be MORE than 3 items. These changes clarify the error messages produced formaxItems,minItems, anduniqueItemserrors.Changeset
Marked as minor due to the change of formatting for maxItems, minItems, and uniqueItems errors.
Issue
See: #171