- Does netbull/doctrine-behaviors work with Laravel Eloquent models?
- No. It is a Doctrine ORM behavior library, not an Eloquent package, and it expects Doctrine entities, metadata, and event subscribers. In an Eloquent-first Laravel app you should use native timestamps, SoftDeletes, UUID or ULID keys, and a slug package instead. Use this package only when your Laravel application already persists data through Doctrine ORM.
- How do I install netbull/doctrine-behaviors in a Laravel Doctrine application?
- Install it with Composer and wire the relevant Doctrine listeners or event subscribers according to the package README. You will also need to confirm your entity mappings and schema conventions for each behavior you enable. It is not drop-in Laravel integration, so plan a small compatibility spike before using it on critical entities.
- Which Doctrine behaviors does netbull/doctrine-behaviors provide?
- The package overview highlights Timestampable, Sluggable, SoftDeleteable, and Blameable as drop-in traits. The technical assessment also references Uuidable, Loggable, Translatable, and Tree, so check the exact behavior set in the README and tagged version you install. Treat Translatable and Tree as higher-risk behaviors because they change schema and query patterns.
- Is netbull/doctrine-behaviors compatible with current Laravel, Doctrine ORM 3.x, and PHP 8.x?
- That compatibility is not confirmed by the provided package context. The assessment recommends building a compatibility matrix for PHP, Doctrine ORM, Doctrine DBAL, Laravel, and any Laravel-Doctrine bridge before adoption. Run a bounded spike on one non-critical entity and pin the package version and commit hash in composer.lock.
- Does netbull/doctrine-behaviors support PHP attributes or only annotations?
- The provided context does not confirm which metadata drivers are supported. It recommends confirming attributes versus annotations, XML, or YAML mapping before integration because attributes are preferable for modern PHP and annotation support is a legacy risk. Verify this against the package README and a test entity in your target stack.
- Can I use SoftDeleteable and Sluggable together safely?
- They can be used together in a Doctrine setup, but you must test event ordering, query filters, and unique slug constraints. The assessment specifically recommends validating SoftDeleteable filters and Sluggable uniqueness before broad adoption. Avoid enabling multiple behaviors on the same entity without confirming generated schema and behavior interactions.
- Should I use netbull/doctrine-behaviors instead of Laravel native timestamps and soft deletes?
- Only if your Laravel application already uses Doctrine ORM for persistence. Eloquent already covers timestamps and soft deletes, and Laravel-native or first-party packages can handle UUID keys, slugs, and audit logging. Introducing Doctrine just to use this package would add architectural mismatch and unnecessary integration effort.
- What production risks should I consider with netbull/doctrine-behaviors?
- The package has weak adoption signals, including zero stars, zero dependents, and a low package score in the assessment. The main risks are compatibility with current Doctrine ORM and PHP versions, maintenance continuity, undocumented behavior interactions, and silent misconfiguration. Treat it as a small-vendor or fork-grade dependency with an exit plan and a compatibility spike before production use.
- How do I migrate existing data for Translatable, Tree, or Loggable behaviors?
- Use Doctrine migrations with explicit backfill scripts, nullability decisions, and rollback steps for existing data. The assessment recommends treating Tree as a separate, higher-risk migration because it changes storage and query patterns. Validate Translatable and Loggable schema impacts carefully, and avoid enabling them broadly until the bounded spike succeeds.
- Is netbull/doctrine-behaviors actively maintained and tested?
- The provided context does not show a tagged release history, test suite, or production evidence. It notes zero stars, zero dependents, and a low package score, so community support is effectively absent. Ask who maintains the fork or package, review its release history and tests, and pin a known version before relying on it.