- Can I install mpp/referential-bundle in a Laravel application?
- Not directly. The package is a Symfony bundle built around Symfony's kernel, dependency injection, and Doctrine-style entities, so it does not plug into Laravel's service provider or Eloquent model. For a Laravel app, treat it as a design reference and reimplement the referential model with Eloquent, backed enums, or a lookup table. Budget one to two weeks for a faithful port.
- How do I install mpp/referential-bundle in a Symfony project?
- The expected flow is Composer require mpp/referential-bundle, register the bundle in config/bundles.php, import its service configuration, and run Doctrine migrations for the provided entities. The overview says the bundle includes Doctrine mappings and DI wiring, but you should verify the exact recipe against the repository because no README excerpt was provided. A half-day spike is a reasonable starting point.
- Does mpp/referential-bundle support Laravel 11 or 12?
- No. There is no Laravel service provider, Eloquent integration, or Laravel version constraint described; the package is explicitly a Symfony bundle. Laravel 11 or 12 compatibility would require a port rather than a configuration change. If you need Laravel-native referentials, use backed enums, config lists, or a lookup table with Filament or Nova.
- What is mpp/referential-bundle used for compared with PHP enums?
- It models hierarchical referentials and entries as database-backed Doctrine entities, with repositories and a service layer for querying reference values. That is useful when reference data changes at runtime, needs parent-child structure, or must be shared across Symfony bundles. PHP backed enums are simpler and safer for fixed, code-level lists that rarely change. For Laravel, enums plus a small lookup table often cover the same need.
- Is mpp/referential-bundle production-ready or actively maintained?
- The available health signals are poor: zero stars, zero dependents, and no evidence of external consumption or release cadence. That does not prove the code is broken, but it means you should expect no external bug reports, no ecosystem pressure to keep the API stable, and uncertain security patching. Check the last commit date, tagged releases, CHANGELOG, and whether the repository is archived before relying on it.
- What are alternatives to mpp/referential-bundle for Laravel lookup tables?
- In Laravel, the native options are backed enums for fixed lists, config-driven arrays for small static dictionaries, and a database lookup table with Eloquent for editable or hierarchical data. Admin surfaces can be built with Filament or Nova, and audit can be added with activity logging packages. The Symfony bundle is not an alternative dependency for Laravel, but its entity model is a useful reference.
- How do I configure the referential entities and service layer?
- Based on the overview, the bundle ships Doctrine mappings, repositories, and a service layer, so configuration is likely bundle registration plus service imports and schema migration. The exact YAML or XML service definitions, entity names, and extension points for custom metadata are not specified in the provided text. Inspect the repository's config directory and tests before assuming an API. For a Laravel port, define your own interface first and keep the model behind it.
- Does mpp/referential-bundle include audit logging or versioning?
- The overview does not mention audit history, versioning, approval workflows, or change tracking. For fintech-adjacent reference data, those are usually required: who changed which value, when, and why. Bundles of this size rarely ship that out of the box, and retrofitting audit onto a foreign data model is expensive. Plan to build audit and versioning yourself, whether you port the model or adopt it.
- How do I seed referential data and keep it fresh?
- The provided overview does not describe fixtures, migrations, import commands, or a seeding strategy. You will need to decide who owns freshness for lists such as currencies, countries, categories, and statuses, because those rot over time. In a Laravel port, use seeders, scheduled imports, and a review workflow for changes. In Symfony, verify whether the bundle expects fixtures or Doctrine migrations before committing.
- What license and dependencies does mpp/referential-bundle have?
- The available context does not include a license file or a dependency list, so confirm both before any use. Check whether it depends only on symfony/framework-bundle or also on Doctrine, API Platform, Messenger, or security components, because each adds integration and upgrade risk. Also check for tagged releases and a CHANGELOG, not just a main branch. License compatibility matters for internal-only and redistributed use.