-
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
Inconsistent syntax for property paths in error objects #818
Comments
I'm guessing we don't want to go with the "expected behavior", but rather just document this? i.e., |
epicfaace
added a commit
to epicfaace/react-jsonschema-form
that referenced
this issue
Jan 20, 2019
9 tasks
epicfaace
added a commit
that referenced
this issue
Mar 6, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Prerequisites
Description
Error objects in the errors collection passed into the transformErrors callback are inconsistent
Field paths have two different syntaxes.
Property keys can delimited by
.
and also encapsulated by[]
when special characters or white space is presentThis may be intentional but it is a breaking change introduced in v1.0.0.
It would be nice to have this noted in the release notes.
Steps to Reproduce
Expected behavior
-> "['firstName']"
-> "['first-name']"
Actual behavior
-> ".firstName"
-> "['first-name']"
Version
1.0.0
The text was updated successfully, but these errors were encountered: