We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi,
I am trying to set a ‘type: [‘null’, ‘object’]’ for a schema item with the below code as an example:
schema={{ type: 'object', properties: { name: { type: 'string', description: 'Name example' }, geometry: { type: ['null', 'object'], properties: { shape: { type: 'string' description: 'Example geometry shape property' }, etc........ } } } }}
When I put this schema into my code it kills my app. Adding in type: 'object' it works fine.
Is it allowed to have type: ['null', 'object'] as I have done in the geometry section above?
both types null and object will be applied to a properties property.
add
{ type: 'object', properties: { name: { type: 'string', description: 'Name example' }, geometry: { type: ['null', 'object'], properties: { shape: { type: 'string' description: 'Example geometry shape property' }, etc........ } } } }
into the schema option of JSON forms
No response
3.4.1
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
Hi,
I am trying to set a ‘type: [‘null’, ‘object’]’ for a schema item with the below code as an example:
When I put this schema into my code it kills my app. Adding in type: 'object' it works fine.
Is it allowed to have type: ['null', 'object'] as I have done in the geometry section above?
Expected behavior
both types null and object will be applied to a properties property.
Steps to reproduce the issue
add
into the schema option of JSON forms
Screenshots
No response
Which Version of JSON Forms are you using?
3.4.1
Package
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: