The current UI object definition (e.g. entities, facets, dialogs) is a bit complicated because it's using a mix of (descriptive) JSON structures and (procedural) chained method invocations. It's also difficult to extend because the definition is written in a function instead of a class.
A proper descriptive object definition language will be useful to define objects without custom code. However, it should be done separately from the code. An object builder will be used to parse the language and construct the object. If an object needs a custom code, it can be done by extending the base class and referring to it from the object definition.
Due to the dynamic nature of the UI and the behavior customization that's required in various parts of the UI, it doesn't seem to be possible to create a purely descriptive object definition language without introducing some sort of logic into the language itself, which then defeats the purpose of a having descriptive language. Objects can still be defined in procedural style using object-oriented JavaScript without introducing too much complexity. I suggest we defer or close this ticket as wontfix.
Metadata Update from @edewata: - Issue assigned to edewata
Login to comment on this ticket.