Core Laravel Package

Getting Started

• This package is a read-only subtree split of lunarphp/lunar, containing only the core domain models and services—not designed for standalone usage. Begin by installing and using the official lunarphp/lunar package (composer require lunarphp/lunar) instead.
• If contributing to Lunar’s core (e.g., PRs, testing), work directly in the main lunarphp/lunar repository. lunarphp/core updates automatically via subtree split and should never be modified manually.
• Your first practical task: explore the src/Models/, src/ValueObjects/, and src/Support/ directories to understand domain primitives like Product, Price, TaxClass, and Currency. These are meant to be extended or composed—not consumed in isolation.

Implementation Patterns

• Extend domain models using Laravel’s Eloquent relationships and traits (e.g., HasPrices, HasTaxClass) on your app’s models—not by forking this package.
• Customize behavior via events and pipelines: listen on PriceCalculated, CartTotalsCalculated, or OrderSubmitted to inject custom logic (discounts, surcharges, audit logging).
• Leverage service provider bindings to override core services (e.g., PriceCalculatorInterface, TaxCalculatorInterface) in AppServiceProvider—ensuring compatibility with the core domain contract.
• Always align custom logic with Lunar’s bounded contexts: cart, catalog, checkout, and pricing are intentionally decoupled—avoid mixing concerns across boundaries.

Gotchas and Tips

• ⚠️ Never require this package in production. It has no versioned releases, no composer.json require section, and no standalone dependencies—attempting to use it directly will break dependency resolution.
• No public repository or issue tracker exists for lunarphp/core—all development happens in lunarphp/lunar. Bugs, feature requests, and docs live there.
• Debugging failures? 99% of issues stem from misconfigured lunar.php (e.g., missing stores, invalid currency locales) or outdated lunarphp/lunar. Ensure the main package is up-to-date first.
• When extending models (e.g., Product), always verify trait usage and foreign key constraints against the parent package’s migrations—this split does not ship its own.
• Ramp-up tip: Run php artisan vendor:publish --provider="Lunar\LunarServiceProvider" to generate config and migrations—even if using only core models—to avoid silent schema mismatches.