Class LaravelUi5\Core\Ui5\AbstractUi5Card

Returns the type of the artifact (e.g., application, library, card).

Returns the parent module of this artifact, if any.

• For Applications, Libraries, Cards, Reports, Tiles, KPIs, Actions and Resources: this returns the Ui5ModuleInterface instance that owns the artifact.
• For Dashboards (global containers outside module scope), this returns null.

Reads the integration-card manifest blade from the host PHP package's resources directory:

/resources/ui5/cards//manifest.json.blade.php

Each card owns a self-contained folder — a canonical sap.ui.integration card package — holding its manifest beside an optional i18n/ bundle (served card-relative by {@see \LaravelUi5\Core\Http\Controllers\CardI18nController}). The .blade.php suffix keeps editors treating the template as Blade rather than (invalid) JSON; the URL-served resource is still manifest.json.

<package-root> is derived from the module class file via reflection (dirname($moduleFile, 2)), so the resolution holds for any module whose class sits at <package-root>/src/<X>.php (the convention the ui5:* generators emit).

Card blades are server-side PHP, so resolution intentionally bypasses the module's source strategy. The source strategy governs UI5 client sources (views, controllers, manifest.json), and a WorkspaceStrategy override points at a separate UI5 workspace directory — which has nothing to do with where the host package's Blade templates live.

Consumers with a non-standard layout (module class not at <package-root>/src/<X>.php) can override getManifest() on the concrete Card and resolve the path however they like.

Default — bare sap.ui.integration.widgets.Card. Concrete cards override to set any Card property they care about (e.g. layoutData for grid sizing); the framework still owns manifest, injected with the server-constructed card-endpoint URL via {@see Card::withManifest()}.

Slot identities this artifact's render (or execution) depends on. The leaf-emitter / consumer passes the list to {@see \LaravelUi5\Core\Parameters\Contracts\ParameterPipelineInterface::resolve()}; unfilled slots throw and propagate up as a typed error.

Values this artifact proposes for the active composition.

Key shape. Slot-name strings (i.e. SomeSlots::Case->value), because PHP forbids BackedEnum cases as array keys at runtime — referencing SomeSlots::Case->value preserves IDE refactor-safety over a raw string:

return [
    CoreSlots::Currency->value => 'CHF',
    CoreSlots::Period->value   => 'quarter',
];

Keep this method lightweight — it's called once per artifact during CompositionParameterSource::fill() for the active dashboard. Return [] to opt out of contributing.