You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not able to properly render data stored inside a json schema key with a special character like a period. I'm using JSONForms.io and React and have tried both the stock material/vanilla renderers and writing my own custom renderer, but when the data is nested within a key like 123.123 it is not properly piped into the ControlProps for access by my custom renderer. Unless there is some way to escape special characters that I am missing this feels like a bug.
Expected behavior
JSON Keys containing periods should properly render in JSON Forms in react.
Steps to reproduce the issue
Build a json blob that has keys containing periods
Try to render that data using JSONForms in React
Observe that it does not work
Screenshots
No response
Which Version of JSON Forms are you using?
3
Framework
No response
RendererSet
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Hi @pjeschba , thanks for raising this issue :)
This is a known bug that is captured and will be solved here: #2153
Thus, I'll close this as a duplicate.
Describe the bug
I'm not able to properly render data stored inside a json schema key with a special character like a period. I'm using JSONForms.io and React and have tried both the stock material/vanilla renderers and writing my own custom renderer, but when the data is nested within a key like
123.123
it is not properly piped into the ControlProps for access by my custom renderer. Unless there is some way to escape special characters that I am missing this feels like a bug.Expected behavior
JSON Keys containing periods should properly render in JSON Forms in react.
Steps to reproduce the issue
Screenshots
No response
Which Version of JSON Forms are you using?
3
Framework
No response
RendererSet
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: