| Cases |
Module = 0
A UI5 module providing a logical container for artifacts such as applications,
cards, tiles, actions, or libraries.…
A UI5 module providing a logical container for artifacts such as applications,
cards, tiles, actions, or libraries. Modules define the namespace scope and slug
used for routing and access control, and typically correspond to a PHP package
or subdirectory within the ui5/ structure.
Modules themselves are not directly routable or versioned as standalone resources,
but serve as the root context for all included artifacts.
|
#
|
Application = 1
A standalone UI5 application with its own routing, Component.js, and entry point.
Typically served as a separate HTML…
A standalone UI5 application with its own routing, Component.js, and entry point.
Typically served as a separate HTML page.
|
#
|
Library = 2
A reusable UI5 library containing controls, formatters, helpers, or shared logic.
Can be imported by multiple…
A reusable UI5 library containing controls, formatters, helpers, or shared logic.
Can be imported by multiple applications.
|
#
|
Action = 3
A backend-bound action that can be triggered via direct API route.
UI5 Actions are invokable controller classes…
A backend-bound action that can be triggered via direct API route.
UI5 Actions are invokable controller classes designed for stateless interaction,
such as toggling flags, triggering workflows, or executing custom business logic.
Actions are uniquely addressable within their module via an HTTP method and route segment.
|
#
|
Report = 4
A server-rendered HTML document, slot-parameterised, shown in `<lux:Report>`.
A server-rendered HTML document, slot-parameterised, shown in <lux:Report>.
|
#
|
Resource = 5
A Resource is a lightweight, read-only UI5 artifact that exposes
structured data for consumption by the client (e.g.,…
A Resource is a lightweight, read-only UI5 artifact that exposes
structured data for consumption by the client (e.g., cards, dashboards, lists).
|
#
|
Dashboard = 6
A dashboard aggregating Groups of Tiles and Cards in a layout.
The Dashboard JSON wire emits a `{ui5.class.name:…
A dashboard aggregating Groups of Tiles and Cards in a layout.
The Dashboard JSON wire emits a {ui5.class.name: properties} UI5
control tree.
|
#
|
DashboardGroup = 7
Composition node between a Dashboard and the Tiles/Cards it
aggregates.
Composition node between a Dashboard and the Tiles/Cards it
aggregates.
|
#
|
Card = 8
A UI5 Integration Card, such as ObjectCard, ListCard, or TableCard.
Usually configured via a manifest and rendered…
A UI5 Integration Card, such as ObjectCard, ListCard, or TableCard.
Usually configured via a manifest and rendered inside a dashboard or shell.
|
#
|
Tile = 9
A Tile definition — single-value visual primitive rendered inside a
Dashboard Group. Each tile provides metadata such…
A Tile definition — single-value visual primitive rendered inside a
Dashboard Group. Each tile provides metadata such as title and
description, and produces a typed UI5 tile control (a Tile —
GenericTile / ActionTile / SlideTile) via its TileProviderInterface
at emission time.
Not routable — tiles are embedded only, never accessed via URL directly.
|
#
|
Chart = 10
A Chart artifact — single visual primitive rendered inside a
Dashboard Group, emitting a {@see \LaravelUi5\Core\Ui5…
A Chart artifact — single visual primitive rendered inside a
Dashboard Group, emitting a {@see \LaravelUi5\Core\Ui5\Controls\Lux\Chart}
DTO carrying an engine-tagged option envelope (ECharts at v0.9).
Not routable — charts are embedded only, listed alongside Tiles
and Cards in a Group's getChildNamespaces().
|
#
|