-
Notifications
You must be signed in to change notification settings - Fork 20
Open
Labels
bugSomething isn't workingSomething isn't workingwontfixThis will not be worked onThis will not be worked on
Description
ℹ️ [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
formcomponent and select it - Insert a valid
schemainto the schema textarea- e.g.
{ "type": "object", "properties": { "foo": { "type": "string" } } } - Insert a valid
uischemainto the uischema textarea- e.g.
{ "type": "VerticalLayout", "elements": [ { "type": "Control", "scope": "#/properties/foo" } ] } - Add an additional property to the
schema- e.g.
{ "type": "object", "properties": { "foo": { "type": "string" }, "bar": { "type": "string"} } } - Extend the
uischemato render the new property- e.g.
{ "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
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingwontfixThis will not be worked onThis will not be worked on
