Sergey Buryndin

@Lily418 @sdirix Are there any ways to avoid using such scopes in uischema now? (like `"#/definitions/AnyElement/anyOf/0/allOf/1"`)

Stefan, thank you for the fast response. But unfortunately I don't understand how can I achieve this without writing custom renderers. Let me explain problem a little more. Suppose we...

I've created [POC ](https://github.com/eclipsesource/jsonforms/pull/1579) how it can be implemented. It can be used like this: `"scope": "$ref/definitions/named_element"`

Hi Stefan, my idea with '$ref' prefix in the scope is not so good, because we also need a data path. POC is completele wrong. Now I see 2 solution...

@sdirix We have implemented [approach 2](https://github.com/eclipsesource/jsonforms/pull/1702). We have been using it successfully for 6 months. Could you please look into it?

You are right. We just return the first found. If user does not agree with this behavior, he can use current approach(with allOf/oneOf/anyOf in the scope). We keep backward compatibility...

@sdirix Are there any thoughts about suggested PR?

@sdirix We have a huge class hierarchy and we describe class properties using JSON schema. We use [exteding](https://json-schema.org/understanding-json-schema/structuring.html#extending) for this. But when we describe uischema we want to have a...

Base class ``` { "id": "/Base", "type": "object", "properties": { "width": { "type": "integer" } } } ``` Child ``` { "id": "/Child", "type": "object", "allOf": [ { "$ref": "/Base"...

@sdirix Are there any thoughts about our use case? > the added functionality is kind of magic, needs to be documented Should we add some documentation to our PR?