atlassian / atlassian/better-ajv-errors
Custom error message based errors do not collect
- Dominant language
- JavaScript
- Stars
- 245
- Forks
- 50
- PR merge metrics
- No merged PRs in 30d
Description
When using the AJV error messages concept, if data is validated against a schema having more than one custom error message defined, and the data has more than one of those errors, only the first one is received back from better ajv errors when the original errors array is parsed.
I will add a schema and data shortly to this issue as well
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by obtaining the promised schema and data, then reproduce the case where multiple AJV custom error messages are present. Trace how the original errors array is parsed and verify that the result includes every matching custom error rather than only the first one.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100