Discriminatormap Bundle Laravel Package

Product Decisions This Supports

• Polymorphic domain modeling: Informs whether to model extensible entity types (e.g., content blocks, account types, workflow steps) through Doctrine single-table inheritance and runtime discriminator-map extension.
• Build vs. buy: Helps decide whether to adopt a small, legacy bundle versus implementing a narrow internal mapping layer or using native framework capabilities.
• Roadmap for legacy PHP/Symfony products: Relevant only if the product already runs Symfony2 + Doctrine ORM 2 and needs dynamic subtype registration without schema or config changes per type.
• Plugin/module extensibility: Supports use cases where modules or tenants register new entity subtypes at runtime, but only within a Doctrine inheritance model.
• Not a Laravel decision: For Laravel/Eloquent products, this package does not support the stack; equivalent decisions should use Eloquent polymorphic relationships, Relation::morphMap(), interfaces, or custom resolution services.

When to Consider This Package

• Consider only when the application is already on Symfony2 with Doctrine ORM 2 and has a concrete need to extend a Doctrine discriminator map dynamically at runtime.
• The team accepts a low-adoption dependency (14 stars, 0 dependents, low package score) and is prepared to vendor, fork, or maintain it internally.
• The need is tactical and narrow; the package is not a strategic platform dependency.
• Look elsewhere if the product is Laravel/Eloquent, uses modern Symfony/Doctrine, requires active maintenance/security support, needs documented SLAs, or can solve the problem with native polymorphic mapping or a small internal resolver.
• Avoid for greenfield products; Symfony2 is end-of-life and this package’s long-term compatibility risk is high.

How to Pitch It (Stakeholders)

Executive summary: This is a small, legacy Symfony2/Doctrine utility, not a Laravel package. It may help a legacy Symfony product support dynamically registered entity subtypes, but its low adoption and end-of-life stack make it a tactical fork-only option, not a strategic dependency. Do not include it in new Laravel roadmaps; use native polymorphic mapping instead.

Engineering summary: The bundle extends Doctrine discriminator maps at runtime. It is only appropriate for an existing Symfony2/Doctrine ORM 2 codebase with a specific polymorphic-entity extensibility need. Budget for internal ownership, compatibility testing, and a migration path. For Laravel, use Eloquent morph maps and polymorphic relationships; for modern Symfony/Doctrine, prefer maintained native patterns or a small in-house resolver.