- Is partitech/sonata-extra compatible with Laravel?
- No. partitech/sonata-extra is built for Symfony applications that use Sonata Admin and Doctrine, not Laravel. Laravel uses Eloquent by default, so direct integration would require adapter code or a separate Symfony service. For a Laravel-first stack, treat it as a framework-mismatch risk.
- How do I install partitech/sonata-extra?
- Install it with Composer using composer require partitech/sonata-extra. You need an existing Symfony application with Sonata Admin and Doctrine configured. Review the package's composer.json for PHP, Symfony, Sonata Admin, and Doctrine version constraints before requiring it. This is not an installation path for a Laravel application.
- What does partitech/sonata-extra do?
- It provides daily-useful helper tools that extend Sonata Admin in Symfony applications. The helpers make it easier to configure, customize, and maintain admin interfaces while reducing common boilerplate. It is positioned as a Sonata and Symfony utility rather than a cross-framework package.
- Which Symfony, Sonata Admin, and Doctrine versions are supported?
- The provided context does not list exact supported Symfony, Sonata Admin, or Doctrine versions. Check the package's composer.json constraints before upgrading. Release 1.0.16 is a patch-level fix for a console error during Doctrine database setup. Confirm that your Doctrine configuration matches the fix's assumptions.
- Does partitech/sonata-extra support Laravel 10 or 11?
- There is no indication of official Laravel 10 or 11 support. The package name and release notes point to Symfony, Sonata Admin, and Doctrine. Laravel teams should evaluate Laravel-native admin packages instead. Direct use in Laravel would be a stack mismatch.
- What changed in version 1.0.16 of partitech/sonata-extra?
- Version 1.0.16 is a patch-level bugfix for a console error during Doctrine database setup. No breaking changes, new features, or deprecations are indicated in the release notes. The version jump from 1.0.14 to 1.0.16 skips 1.0.15, so review the diff or linked PR. Risk is low for existing Symfony and Doctrine consumers.
- Can I use partitech/sonata-extra with Eloquent instead of Doctrine?
- No. The package references Doctrine database setup and targets Sonata Admin, which is Doctrine-oriented. Eloquent integration is not described or supported. Using it with Eloquent would require custom adapter work or a separate Symfony service, which is likely disproportionate for the value.
- How do I test partitech/sonata-extra in a staging environment?
- Pin your current working version and run your existing test suite first. Reproduce the Doctrine database setup console error if it applies to you. Apply 1.0.16 in staging and re-run setup or migration commands. Promote to production only after those checks pass, and avoid bundling unrelated framework or ORM upgrades.
- Is partitech/sonata-extra actively maintained and production-ready?
- Release notes are terse and the provided context does not detail maintainer cadence or long-term support. Support appears to be the GitHub repository and community PRs. For Symfony and Sonata consumers the package looks plausible and this patch is low risk. Laravel consumers face high maintenance burden because the package sits outside the native ecosystem.
- What are the alternatives to partitech/sonata-extra for Laravel?
- For Laravel, consider Laravel-native admin packages such as Filament, Laravel Nova, Backpack, or Orchid. These align with Eloquent and Laravel conventions. Avoid directly integrating Symfony and Sonata packages unless a Symfony sidecar is already part of your architecture. A sidecar only makes sense with a compelling cross-framework requirement.