Chiron Laravel Package

Product Decisions This Supports

• Core 3.0 upgrade planning: v1.3.0 is effectively a compatibility release for the Laravel UI5 ecosystem. Treat it as a planned migration item, not a drop-in patch, if you scaffold modules/actions or rely on settings context.
• Scaffolding and developer-experience decisions: laravelui5-modules now requires explicit identity options (--package-prefix, --php-ns-prefix, and --vendor for apps). This supports decisions about standardizing project generation, CI templates, and onboarding scripts around core 3.0 conventions.
• Namespace and code-organization standards: laravelui5-actions scaffolds kebab-case namespaces going forward (actions.clear-mailbox), while existing snake_case namespaces remain valid. This supports a phased convention migration rather than a forced rename.
• Settings/context behavior expectations: Settings now reach Tile, Chart, and Report providers, and writing to a setting throws. This affects product behavior around runtime configuration, reporting/chart/tile customization, and error handling.
• Currency-slot removal: The base currency is no longer a slot; slot examples are locale, time zone, and period, and slot values come from the query string only. This supports decisions about localization/context modeling and any UI that previously relied on a currency slot.
• Build vs. buy: For Laravel teams integrating SAP UI5, this package remains a candidate to accelerate module/action scaffolding and context/settings integration, provided the team can absorb core 3.0 migration requirements.

When to Consider This Package

• Consider it when you are building or maintaining a Laravel application with a SAP UI5 frontend, especially if you want scaffolding for UI5 modules/actions and a structured settings/context layer.
• Consider it when you are already on the Laravel UI5 ecosystem and are planning to adopt core 3.0, or are starting fresh on core 3.0 and want conventions aligned with the current release.
• Be cautious when you are still on core 2.x and cannot yet migrate: v1.3.0 documents behavior that follows core 3.0, including required scaffolding identity options and changed settings semantics.
• Look elsewhere or defer when you do not use UI5, when your tooling depends on the old scaffolding defaults, when you rely on a base-currency slot, or when you cannot tolerate settings writes throwing in provider contexts.
• Migration gate: Audit generated project scripts, CI jobs, namespace expectations, and any code that writes settings from Tile/Chart/Report providers before adopting.

How to Pitch It (Stakeholders)

• For executives: This release keeps the Laravel UI5 package aligned with core 3.0 and improves consistency in how UI5 modules, actions, and settings are generated and consumed. It is valuable for teams standardizing on the current UI5 integration stack, but it requires a short migration plan rather than an automatic upgrade.
• For engineering: v1.3.0 introduces breaking-ish changes: scaffolding now requires identity flags, new action namespaces use kebab-case, settings propagate to all providers and setting writes throw, and the currency slot is removed. Update scaffolding commands, CI templates, namespace conventions, and settings write paths before upgrading. Existing snake_case action namespaces remain valid, which enables a phased rollout.
• Product recommendation: Adopt as part of a core 3.0 migration initiative, with explicit validation of generated modules/actions and settings-driven UI behavior. Do not treat this as a silent patch release.