Dynamic Orm Value Bundle Laravel Package

Product Decisions This Supports

• Dynamic Data Generation: Enables automatic generation of derived or computed fields (e.g., user-friendly IDs, timestamps, or metadata) during entity persistence, reducing manual logic in business layers.
• Decoupling Business Logic: Shifts field population from application code to ORM-level configuration, simplifying controllers/services and improving maintainability.
• Roadmap for "Smart Defaults": Supports future features like conditional dynamic values (e.g., auto-generating slugs only for published content) or integration with workflows (e.g., audit trails).
• Build vs. Buy: Avoids reinventing wheel for dynamic field logic; leverages a lightweight, MIT-licensed solution instead of custom development.
• Use Cases:
  • User Experience: Generate readable IDs (e.g., ORD-2024-001 instead of 12345).
  • Compliance: Auto-populate timestamps or status flags (e.g., created_at, is_active).
  • Multi-Tenant Systems: Inject tenant-specific metadata dynamically.

When to Consider This Package

• Adopt When:
  • Your Symfony/Doctrine app requires repeated dynamic field generation (e.g., >3 entities with similar patterns).
  • You prioritize cleaner controllers/services by offloading field logic to the ORM.
  • Your team lacks bandwidth to build/maintain custom dynamic-field logic.
  • You need consistent behavior across environments (dev/staging/prod).
• Look Elsewhere If:
  • Your dynamic logic is highly complex (e.g., involves external API calls or async processing)—consider a service layer or event listeners.
  • You’re using non-Doctrine ORMs (e.g., Eloquent, Propel).
  • You need real-time updates (this runs on persist, not update).
  • Your team prefers runtime flexibility over compile-time annotations (e.g., dynamic values via API calls).

How to Pitch It (Stakeholders)

For Executives: "This bundle lets us automate repetitive field generation (e.g., user-friendly IDs, timestamps) directly in the database layer, cutting dev time and reducing bugs. For example, instead of manually setting order_code in every order creation flow, it auto-generates ORD-2024-001. It’s a low-risk, MIT-licensed tool that aligns with our Symfony stack—think of it as ‘set-and-forget’ for derived data."

For Engineers: *"A lightweight Symfony bundle that uses Doctrine lifecycle events to populate fields dynamically via #[DynamicValue] annotations. No need for custom listeners or service logic—just configure it once in dm_dynamic_orm.yaml and annotate entities. Ideal for:

• Boilerplate reduction: Remove setCreatedAt() calls from 20+ entities.
• Consistency: Ensure slug fields are always lowercase and hyphenated.
• Future-proofing: Easy to extend with custom generators (e.g., UUIDs, hashes). Tradeoff: Limited to persist-time logic (not updates), but saves ~5–10 LOC per entity."*