Symfony Password Exposed Bundle Laravel Package

Getting Started

1. Install the package with Composer and confirm your app satisfies the advertised matrix: PHP 7.4 through current PHP, Symfony 4.4 through Symfony 8.
2. Look first at:
   • README.md for registration and YAML examples.
   • The bundle/service-provider class, especially build().
   • The documented configuration reference. v1.1.0 corrects and clarifies YAML defaults, so treat the new docs as authoritative.
   • The regression tests for “lowest” and “current” dependency configurations.
3. First use case: register the bundle/provider, import the documented YAML config, and resolve the translation contract from the container rather than a concrete translator. Run the app’s container compile and a basic translation lookup to confirm wiring.

Implementation Patterns

• Register the bundle normally, then publish or import only the configuration you actually override. Rely on the documented defaults instead of copying the full YAML tree.
• When extending the bundle with compiler passes, follow the v1.1.0 pattern: call the parent bundle build hook before registering your own passes.
• Type-hint the translation contract, not a concrete translator implementation. This keeps cross-version resolution stable across Symfony 4.4 through 8.
• In CI, test both lowest and current dependency sets. The release adds explicit lowest/current configuration regression coverage, so mirror that in your own integration tests.
• For Laravel apps using Symfony components through a bridge, bind the translation contract in a service provider and keep configuration defaults centralized. Avoid hard-coding translator class names.
• Treat v1.1.0 as a compatibility and correctness release: no obvious new feature surface, but meaningful improvements for supported-version breadth, config defaults, and extension ordering.

Gotchas and Tips

• Do not skip parent::build() in a custom bundle. v1.1.0 specifically fixes ordering so parent build runs before compiler passes are registered; skipping it can cause missing container wiring.
• Re-check existing YAML overrides after upgrading. Defaults were corrected and clarified, so old assumptions may no longer match runtime behavior.
• Do not commit the package’s obsolete lockfile. It was removed because it pinned stale dependencies; let your application’s root lockfile and CI matrix control resolution.
• If you support both PHP 7.4 and Symfony 8, verify Composer constraints carefully. The release claims broad compatibility, but your own dependency graph may still block it.
• Debug container issues with Symfony’s container/config debugging tools where available, and inspect the bundle build order if services or compiler passes are missing.
• Extension points to watch: bundle build hooks, compiler passes, configuration tree/defaults, and translation-contract bindings. These are the areas most affected by this release.