Package io.jmix.dynmodelflowui.impl
package io.jmix.dynmodelflowui.impl
-
ClassDescriptionResolves a registered view id to the XML descriptor of the underlying static view.A resolved static view: the descriptor path usable as an
extendsvalue, and the parsed root element of that descriptor.Builds dom4j elements (columns and form components) for dynamic attributes of a static entity, driven by the Admin-UIDynamicAttributeModelrather than runtimeMetaProperty.Adds dynamic model bean-group validation to Flow UI view validation.Converts dynamic model definitions between YAML content, immutable metadata definition records and mutable model entities used by the Admin UI graphical editor.Resolves whether a model entity name refers to a static-entity extension rather than a dynamic entity.Resolves the runtime template-generated view ids (@ListViewTemplate,@DetailViewTemplateand@ReadViewTemplate) owned by a static entity.Adds dynamic model validators to Flow UI value components bound to dynamic properties.Lists the components available in a dynamic view declaration, so the behavior handler editor can offer them instead of asking the user to type an id.A component offered by the handler editor: itsidand the XMLtagit was declared with, such asbuttonortextField.Lists the attributes reachable throughentityin a behavior handler expression, so the Admin UI can offer them as code completion.Signals that a view extension could not be generated.Generates a<view extends="…">extension XML that adds a static entity's dynamic attributes to an existing view, targeting thedataGrid(columns) orformLayout(components) bound to the entity's data container.Works out what the cursor stands in the middle of in a behavior handler expression, so the Admin UI can decide what to offer as code completion.One open call while scanning: its receiver, its name, and how many arguments were closed by a comma.Provides code completion for a dynamic view behavior handler expression, in the roleJpqlUiSuggestionProviderplays for JPQL queries.What the editor knows about the handler being edited and cannot be derived from the expression.Generates the literal XML source of a template-based dynamic entity view, so the Admin UI can offer "render the template, then edit the XML by hand" instead of writing a descriptor from scratch.Resolves the registered views that work with a given entity.Answers which behavior handler triggers a view XML tag can serve, so the Admin UI handler editor can offer only the components a trigger can actually attach to.What a tag can be used for.