Stefan Dirix

Hi @freddie-95, thanks for the report! I can reproduce the issue. I don't know yet where this problem comes from and whether this is a JSON Forms issue or a...

Thanks for the analysis! We'll take a look. In case you need a workaround until the fix is done you can use [`json-refs`](https://www.npmjs.com/package/json-refs) to resolve your JSON Schemas before handing...

Within the combinator mappings we try to determine the best fitting schema so that the renderer can decide which tab to show. With the removal of the auto-resolving this no...

Hi @jaguirre-pricesmart, I'm not sure that I can follow. We are using the `type` attribute where necessary, see for example [here](https://github.com/eclipsesource/jsonforms/blob/8dc8751717e8680568fe4e0da713786b0202b2fe/packages/vue/vue-vanilla/src/controls/DateTimeControlRenderer.vue#L9) and [here](https://github.com/eclipsesource/jsonforms/blob/8dc8751717e8680568fe4e0da713786b0202b2fe/packages/vue/vue-vanilla/src/controls/IntegerControlRenderer.vue#L9). Is there something I'm missing?

Closed as there was no more information. Feel free to reopen when needed.

Hi @neuralsea-lab, thanks for the report! JSON Forms doesn't [handle special characters like `/` and `~` properly](https://tools.ietf.org/html/rfc6901#section-4). The ui schema generator needs to improved to detect these characters and encode...

ToDo: - Adapt the ui schema generator, to properly encode the special characters in the `scope`. The ui schema generator code is [here](https://github.com/eclipsesource/jsonforms/blob/38153357a5b6dc0a02d940199fb71121f4197001/packages/core/src/generators/uischema.ts). - Adapt the resolving code to properly...

In general yes as anything in JSON Forms is customizable, however there is no specific support. We use the scope in two ways: - Resolving the corresponding part in the...

Hi @buryndin, thank you very much for the POC! Can you give a concrete example on how the POC is intended to be used? Just by quickly looking at it...

@buryndin So what do you do when the scope is no longer uniquely identifying the property because the `allOf`, `oneOf` or `anyOf` is missing? Do you just return the first...