Package com.onec.ui
Class UiViewResolver
java.lang.Object
com.onec.ui.UiViewResolver
Resolves a per-entity
EntityView (authored in code) over the
auto-generated metadata defaults into a renderer-agnostic ResolvedListView.
Entities without an EntityView fall back entirely to the defaults (system +
visible custom columns, in field-hint order), so adding a view is purely
additive. The DivKit emitter compiles the result; the model is renderer-neutral.-
Constructor Summary
ConstructorsConstructorDescriptionUiViewResolver(ResolvedMetadataService metadata, List<EntityView> entityViews) -
Method Summary
Modifier and TypeMethodDescriptioncatalogList(CatalogDescriptor d, String profileId) booleancommentsEnabled(Class<?> entity) Whether comments are enabled for this entity — true if any of its views (default or profile-specific) opts in viaEntityView.comments().documentList(DocumentDescriptor d, String profileId) booleanWhether this entity is declared by a view (profile-specific or default) and may therefore appear in the UI.
-
Constructor Details
-
UiViewResolver
-
-
Method Details
-
catalogList
-
documentList
-
hasView
Whether this entity is declared by a view (profile-specific or default) and may therefore appear in the UI. The view layer is the allowlist: an entity with no view is hidden from nav and its surfaces 404 — only what's authored renders. -
commentsEnabled
Whether comments are enabled for this entity — true if any of its views (default or profile-specific) opts in viaEntityView.comments(). The comment panel and the/api/commentsendpoint are both gated on this, so comments are an opt-in, per-entity capability (on top of the globalonec.comments.enabledswitch). Resolved at the entity level, not per profile.
-