Weave Code
Simple Metadata Bundle Laravel Package
idci/simple-metadata-bundle
A small Symfony bundle for attaching simple metadata to your objects, letting you store extra key-value data alongside entities without schema changes. Lightweight and easy to wire into existing projects, though it has minimal adoption and may need review before production use.
Symfony SimpleMetadataBundle
Frequently asked questions about Simple Metadata Bundle
- Is idci/simple-metadata-bundle a Laravel package?
- No. It is a Symfony bundle built around Doctrine ORM and Symfony's service container, and it ships no Laravel service provider, facade, publishable config, or Eloquent integration. Installing it in a Laravel app would not wire up any usable behavior.
- Can I use IDCI SimpleMetadataBundle with Laravel Eloquent models?
- Not directly. The bundle persists metadata through Doctrine entities and a polymorphic side table, while Eloquent uses its own model layer, query builder, and morph relations. You would need to reimplement the pattern natively rather than reuse the bundle code.
- How do I install idci/simple-metadata-bundle?
- It is installed with Composer as idci/simple-metadata-bundle and then registered as a Symfony bundle in your kernel. Its composer constraints target Symfony2-era PHP and Doctrine versions, so a modern Laravel or Symfony install will likely conflict. A --ignore-platform-reqs install is not a safe workaround.
- What Laravel version does idci/simple-metadata-bundle support?
- None. The package predates and does not target Laravel at all; it is a Symfony2 bundle. There is no supported Laravel 9, 10, or 11 path, and its dependency constraints conflict with modern PHP 8+ applications.
- What are alternatives for storing arbitrary metadata on Laravel models?
- Common Laravel-native options include a JSON column with an Eloquent cast, spatie/laravel-schemaless-attributes, or a small polymorphic metadata table paired with a HasMetadata trait. Each is simpler to maintain than porting a Symfony bundle and can be tested inside your existing stack.
- How does IDCI SimpleMetadataBundle store metadata without changing entity schema?
- It uses a Doctrine-based side table keyed by the owning object's type and identifier plus a metadata key, so the original entity table stays unchanged. A service layer reads, writes, and queries those records. The idea is reusable, but the shipped implementation is tied to Doctrine and Symfony wiring.
- Can I query entities by metadata value with this bundle?
- The bundle provides a service API for reading, writing, and querying metadata, but the exact query support and indexing are not a substitute for designing your access patterns. If you need frequent find-all-X-where-metadata-Y-equals-Z queries, plan your own schema and composite indexes. Verify the source before assuming the bundle covers it.
- Is idci/simple-metadata-bundle maintained and production ready?
- It has minimal adoption, very few stars and dependents, and targets Symfony2, which reached end of life in 2018. There is no modern security patch path and little community validation. Treat it as prior art or a reference pattern, not a production dependency.
- What PHP and Symfony versions does the bundle require?
- Expect Symfony2-era constraints, typically PHP 5.6 or 7.0 with symfony/* 2.x and contemporary Doctrine ORM and DBAL versions. Those constraints hard-conflict with Laravel 9+ and PHP 8+, and forcing resolution can surface removed PHP APIs at runtime. Check the composer.json before any spike.
- How should a Laravel team evaluate or port this bundle?
- Run a short spike to confirm the requirement is real and to identify read versus query access patterns. If you need the functionality, build a native Laravel version: a metadata table with metable_type, metable_id, key, value, type, timestamps and a composite index, a HasMetadata trait, a Metadata model, a service provider, and tests. Budget a few engineering days rather than depending on the Symfony bundle.
Weaver
How can I help you explore Laravel packages today?