-
Notifications
You must be signed in to change notification settings - Fork 361
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
Unify path handling #2153
Milestone
Comments
This was referenced Jun 29, 2023
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At the moment we maintain two different paths in JSON Forms:
scope
JSON Pointer paths used in UI Schema to resolve to subschemas of the handed over JSON Schemapath
paths (lodash format) to resolve to entries in the form-widedata
objectThe JSON Pointers are well defined and JSON Forms support escaping of their special characters (
/
and~
).The dot-separated
path
s however don't support escaping, leading to errors when a.
is contained within the path. This was already reported in #1631 and #1849To fix the issues and to harmonize path handling in JSON Forms we should settle on JSON Pointers for all paths. As a consequence data paths would change from
person.name
to/person/name
.Benefits:
Downside:
Therefore it should be released only with a 4.0 version and be mentioned in the MIGRATION guide.
The text was updated successfully, but these errors were encountered: