Interface LaravelUi5\Core\Ui5\Dashboard\Contracts\Tile

Marker narrowing {@see WireElement} to tile-root shapes — the controls a {@see \LaravelUi5\Core\Ui5\Capabilities\TileProviderInterface} may return as a dashboard tile: sap.m.GenericTile, sap.m.ActionTile (which extends GenericTile), and sap.m.SlideTile (a container that cycles through GenericTiles).

Parallels {@see Payload} — Payload marks the content controls that sit inside a tile's tileContent (sap.m.NumericContent, …); Tile marks the tile itself. The {@see \LaravelUi5\Core\Ui5\Capabilities\TileProviderInterface} returns this marker rather than a closed GenericTile|ActionTile|SlideTile union, so a future tile type only has to implements Tile — no signature change ripples out. The real gate on what may render is the client vocabulary in ui5-core-lib's Dashboard control, which refuses any ui5Class outside its declared map.

╔══════════════════════════════════════════════════════════════════════╗ ║ PINNED TO OpenUI5 1.136.x ║ ║ ║ ║ The tile vocabulary (GenericTile / ActionTile / SlideTile) and ║ ║ every property seat on the concrete DTOs is modelled against ║ ║ OpenUI5 1.136 — the version the bundled ui5-core-lib ship ║ ║ against. sap.m.ActionTile only exists since 1.122; ║ ║ sap.m.SlideTile since 1.34. Before adding or changing a property, ║ ║ verify it against the 1.136 API reference (the ui5-mcp server's ║ ║ get_api_reference) — NOT training recall. ║ ╚══════════════════════════════════════════════════════════════════════╝