Weave Code
Tag Bundle Laravel Package
lendable/tag-bundle
Lendable TagBundle provides Doctrine-backed tagging for Symfony apps. Add a Taggable interface to any entity, then use the included Tag and Tagging entities and manager services to attach, detach, and query tags without building custom tag storage or relationships.
tag entities
Frequently asked questions about Tag Bundle
- Can I use Lendable TagBundle in a Laravel app?
- Not cleanly. Lendable TagBundle is a Symfony bundle tied to Symfony's service container and Doctrine ORM, so it does not install into Laravel's Eloquent and migration model. For Laravel, implement the same concept natively: a tags table, a polymorphic pivot with taggable_type and taggable_id plus tag_id, a unique composite index, and an Eloquent trait using morphToMany. That gives you identical capability with native migrations and no container coupling.
- Is Lendable TagBundle a Symfony bundle or a Laravel package?
- It is a Symfony bundle. The repository name Lendable TagBundle and the Bundle suffix, plus its Symfony service container configuration and Doctrine ORM integration, point to Symfony rather than Laravel. The brief's Laravel framing is likely a mislabel; treat it as Symfony/Doctrine unless the source proves otherwise.
- How do I install and configure Lendable TagBundle?
- Install it with composer require lendable/tag-bundle, enable the bundle in your Symfony kernel or bundles.php, and configure the tag and tagging entity classes to match your domain. The overview says configuration is quick, but the provided excerpt does not include the README or exact config keys. Read the bundle's README and source for required entity mappings and service IDs before adopting.
- What is the Taggable interface and how does it work?
- The Taggable interface marks a Doctrine entity as taggable. You implement it on any entity that should receive tags, then use the bundle's manager services and included Tag and Tagging entities to attach, detach, and query tags. This avoids custom tag storage and relationship code, but you must confirm the exact method signatures and mapping style in the source.
- Does Lendable TagBundle support polymorphic tagging across multiple entity types?
- The overview says arbitrary Doctrine entities can be tagged and that tagging entities are configurable, which implies multi-entity support. It does not explicitly state whether the schema uses polymorphic taggable_type and taggable_id columns or a fixed foreign key. That distinction matters for multi-entity roadmaps, so verify the Tagging entity mapping before committing.
- Which PHP, Symfony, and Doctrine versions does Lendable TagBundle support?
- The provided overview does not specify PHP, Symfony, or Doctrine version constraints. Those are declared in composer.json, so check it for the minimum PHP version, Doctrine ORM range, and Symfony bundle version. With zero stars and no visible release cadence, also check whether those constraints are current against the next major releases.
- Does Lendable TagBundle create its own database tables and migrations?
- The bundle ships Tag and Tagging entity classes, but the overview does not say whether it owns schema and migrations. If it owns tables, you inherit its naming, index, and evolution decisions and cannot diverge without a data migration. If it ships only entity classes, you control the schema. Confirm this before adoption because it is the main coupling risk.
- How do I query or filter entities by tag with Lendable TagBundle?
- The bundle provides repository and query helpers for filtering tagged records, and manager services for attaching and detaching tags. The exact API is not in the provided excerpt, so check the repository for helper method names and whether filtering is done through the Tag entity or a taggable repository. In a Laravel port, the equivalent is whereHas on a morphToMany tags relation.
- Is Lendable TagBundle safe and maintained enough for production?
- Treat it as high process risk and low technical risk. It has zero stars, zero dependents, a one-line description, and no documented adoption or release cadence, so it is a candidate to go stale against the next PHP or Doctrine major. Supply chain risk also applies because an unvetted Composer dependency runs its full transitive tree in-process. The mitigating factor is that the domain is trivial: an interface, a trait, and a tag entity are portable by inspection, so replacement is a day or two rather than a rewrite.
- What are the best alternatives for tagging in Laravel or Symfony?
- For Laravel, do not install this bundle; build native morph tagging with a tags table, a polymorphic pivot, an Eloquent trait, and migrations. For Symfony/Doctrine, compare a maintained Doctrine taggable package or vendor this bundle's entity definitions as source rather than depending on it as supported infrastructure. The actual test is whether you have more than one entity type on the near roadmap that needs labels; if not, a generic tagging layer may not earn its keep.
Weaver
How can I help you explore Laravel packages today?