-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
explicit ajv stack error #2634
explicit ajv stack error #2634
Conversation
…alse doesn't remove extra data
…alse doesn't remove extra data
@epicfaace if we bump the major version for my PR, maybe adding this one in at the same time makes sense? |
@Lausselloic in the upcoming @rjsf v5 release the |
@Lausselloic So the v5 beta is now the master branch... Please consider porting this to the |
Closing due to reimplementation in #3337 |
Reasons for making this change
Improve the error format from AJV. Currently it return a dotted path from schema like
.foo.bar.mycustomProp is a required property
into the stack error. What I ropose is to fetch "display" name of the property if it existstitle
or the property himself otherwise. It's more human readable and it's whats is needed for a user interface I think.Related to #1337 need to enbale verbose mode of AJV
User could still create the old message by using Property and message returned into the error field
If this is related to existing tickets, include links to them as well. Use the syntax
fixes #[issue number]
(ex:fixes #123
).Checklist