Faq Bundle Laravel Package

Getting Started

Release 4.0.1 is a compatibility patch: it adds Symfony 4.3 support. Treat it as a dependency/compatibility update, not a feature release. Start by confirming your app’s Laravel and Symfony component versions with composer show and composer why symfony/.... Update with composer require vendor/package:^4.0 --with-dependencies or composer update vendor/package --with-dependencies, then run the package’s documented smoke test. First place to look is the package service provider and published config; first use case is resolving the package’s main service/contract from the container in a small feature test. If you are not on Symfony 4.3, do not downgrade just to adopt this patch.

Implementation Patterns

• Dependency upgrade pattern: update only this package and its lock entries; inspect composer.lock for Symfony component changes. Use composer why-not symfony/console 4.3.* to diagnose conflicts.
• Laravel integration pattern: bind package contracts in a service provider, inject them into controllers/jobs/commands, and keep package calls behind a small adapter if the package is used widely.
• Config pattern: publish config only when you need overrides; prefer env vars for environment-specific values; run php artisan config:cache only after verifying.
• Test pattern: add a feature test that boots Laravel, resolves the package service, and exercises one real workflow. If supporting Symfony 4.3, include it in CI alongside your current Symfony version.
• Version-pinning pattern: keep composer.json constraints explicit enough that patch releases cannot silently move Symfony components outside your supported matrix.
• Extension pattern: use documented extension points such as custom drivers, macros, events, or container bindings rather than editing vendor code.

Gotchas and Tips

• Symfony 4.3 is old/EOL; compatibility support does not imply security support. Prefer newer Symfony versions where your Laravel version allows.
• A patch version can still change Composer constraints; review the diff after update, not just the release note.
• Laravel and the package may both depend on Symfony components; direct Symfony dependencies in your app are the usual source of resolution conflicts.
• After updating, clear config/route/view caches and run composer dump-autoload; stale container/config caches can look like package bugs.
• Debug container issues with php artisan tinker or a small test that resolves the binding; check package logs and config merge order.
• Do not assume Symfony 4.3 support means Symfony 5/6 support; verify each major Symfony line separately.
• If the package publishes config or migrations, commit those changes deliberately and avoid publishing over existing customizations.