- How do I install symfonyboot/symfonyboot-bundle?
- Install the bundle with Composer using composer require symfonyboot/symfonyboot-bundle. Register the bundle in your Symfony application and add any provided configuration under config/packages. Check the package's composer.json for PHP and Symfony version constraints before installing.
- Is symfonyboot/symfonyboot-bundle compatible with Laravel?
- This is a Symfony bundle, so it is not designed around Laravel's service container or package discovery. A Laravel team would need to adapt its Symfony service definitions and configuration manually. The TPM assessment flags the serializer swap as high risk and only reasonable if the package provides Laravel-friendly provider and config bindings, so treat it as Symfony-first unless the README documents Laravel support.
- What Symfony and PHP versions does symfonyboot-bundle support?
- The supplied overview does not list exact Symfony or PHP version constraints, so verify them in the package's composer.json and README. The TPM assessment notes that v3.0.0 is a breaking major upgrade and calls for checking supported PHP versions and JMS Serializer constraints. Also confirm any transitive dependency requirements before upgrading.
- What changed in symfonyboot-bundle v3.0.0?
- The TPM assessment describes v3.0.0 as a breaking major upgrade that replaces Symfony Serializer with JMS Serializer and adds array-of-objects support. Expect changes in configuration style, metadata handling, exclusion policies, naming strategies, date handling, enums, and custom normalizers. Do not treat v3.0.0 as a drop-in upgrade from the prior major.
- Does symfonyboot-bundle replace Symfony Serializer with JMS Serializer?
- According to the TPM assessment, yes: v3.0.0 changes the serialization model to JMS Serializer. That means attribute or annotation metadata, cache setup, and extension points differ from Symfony Serializer. Audit any direct references to Symfony Serializer classes or normalizers before upgrading.
- How do I configure JMS Serializer metadata caching with symfonyboot-bundle?
- JMS Serializer requires explicit metadata cache configuration and cache warmup, which the TPM assessment flags as an operational concern. Configure a writable cache directory for your Symfony environment and verify it works during deploy warmup. Test the setup with your config cache and deployment pipeline. Check the bundle README for the exact cache service or configuration keys.
- How should I migrate from Symfony Serializer to JMS Serializer with this bundle?
- Pin the current major in production, create a migration branch for v3.0.0, and inventory DTO attributes, custom normalizers, encoders, exclusion rules, naming strategies, and date handlers. Replace Symfony Serializer customizations with JMS equivalents and add golden-payload tests for arrays, nested DTOs, dates, enums, errors, and null values. Use a feature flag or parallel-run payload diff before broad rollout.
- What are the production risks of using symfonyboot-bundle?
- The main production risk is output shape drift after the serializer swap, including date and time handling, exclusion policies, naming strategies, circular references, and custom handlers. JMS metadata cache issues can also break deploys if permissions or warmup are incorrect. Run contract tests and a canary with payload diffing before broad rollout.
- Is deserializing untrusted input safe with symfonyboot-bundle?
- The TPM assessment specifically calls for a security review of JMS metadata-driven hydration when untrusted input reaches deserialization. The provided overview does not document protections or supported deserialization modes. Avoid accepting untrusted payloads until you confirm the bundle's safeguards and validate input separately.
- What alternatives exist to symfonyboot-bundle for REST API bootstrapping?
- For Symfony, the standard Symfony Serializer with API Platform or FOSRestBundle are common alternatives for REST API work. For Laravel, use Eloquent API resources, Symfony Serializer integration packages, or API Platform where appropriate. Compare serializer configuration burden, metadata caching, and extension points before choosing an alternative.