-
Notifications
You must be signed in to change notification settings - Fork 0
feat: ✨ handle grouped errors under resource fields #175
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
If we merge in #177, I will align this with that |
lwjohnst86
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! Only some small comments
lwjohnst86
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very small change to the error message
lwjohnst86
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Description
This PR adds a function for handling grouped errors under
$.resources[x].schema.fields[x].Here, the problem comes from the fact that each field type has its own sub-JSON-schema, and each one of these sub-schemas flags issues when the type of a field is not its own type. So, if a field has
type="number"and there is something wrong with the field, then the sub-schemas foryear,string, etc. will also flag issues. The goal is to flag issues only fornumber.Part of #15
Needs an in-depth review.
Checklist
just run-all