ℹ️ [Has been added as a workaround for #181 ]
Describe the bug
Currently json-forms/vue2 has a bug (eclipsesource/jsonforms#1726) that the renderers are not reacting in the right way to active changes to schema or uischema.
Also the sha256.js file has been added to ensure that the key-string is kept short.
This lib can portentially be removed then too.
Until this is fixed we will have to keep this workaround but as soon as the issue is resolved we should upgrade and remove this workaround
To Reproduce
Steps to reproduce the behavior:
- Create a tenant
- Go on any page (e.g. Home)
- Insert a
form component and select it
- Insert a valid
schema into the schema textarea
{
"type": "object",
"properties": {
"foo": {
"type": "string"
}
}
}
- Insert a valid
uischema into the uischema textarea
{
"type": "VerticalLayout",
"elements": [
{
"type": "Control",
"scope": "#/properties/foo"
}
]
}
- Add an additional property to the
schema
{
"type": "object",
"properties": {
"foo": {
"type": "string"
},
"bar": { "type": "string"}
}
}
- Extend the
uischema to render the new property
{
"type": "VerticalLayout",
"elements": [
{
"type": "Control",
"scope": "#/properties/foo"
},
{ "type": "Control", "scope": "#/properties/bar" }
]
}
- You will now see:
Expected behavior
It should render the new prop properly without having to use :key
Describe the bug
Currently json-forms/vue2 has a bug (eclipsesource/jsonforms#1726) that the renderers are not reacting in the right way to active changes to
schemaoruischema.Also the
sha256.jsfile has been added to ensure that the key-string is kept short.This lib can portentially be removed then too.
Until this is fixed we will have to keep this workaround but as soon as the issue is resolved we should upgrade and remove this workaround
To Reproduce
Steps to reproduce the behavior:
formcomponent and select itschemainto the schema textarea{ "type": "object", "properties": { "foo": { "type": "string" } } }uischemainto the uischema textarea{ "type": "VerticalLayout", "elements": [ { "type": "Control", "scope": "#/properties/foo" } ] }schema{ "type": "object", "properties": { "foo": { "type": "string" }, "bar": { "type": "string"} } }uischemato render the new property{ "type": "VerticalLayout", "elements": [ { "type": "Control", "scope": "#/properties/foo" }, { "type": "Control", "scope": "#/properties/bar" } ] }Expected behavior
It should render the new prop properly without having to use
:key