Route Autofill Bundle Laravel Package

Product Decisions This Supports

• Framework scope correction (material): Despite being filed under "Laravel/PHP," rollerworks/route-autofill-bundle is a Symfony bundle, not a Laravel package. Any roadmap item assuming drop-in Laravel usage should be re-scoped or dropped before it reaches estimation.
• Feature enablement: The package's job is to automatically supply route parameters when generating URLs (the "sticky parameter" pattern — locale, tenant, account, or similar context values carried across links without repeating them in every path() call). This is a template/controller boilerplate-reduction feature, not a platform capability.
• Build vs. buy: The value proposition is thin. A request-scoped listener or a small URL-generator decorator replicates the core behavior in a few hours. Adopt only if you are already on Symfony and want the convention out of the box; otherwise building in-house gives you full control and no pre-1.0 dependency risk.
• Version-currency signal: v0.1.2 adds Symfony 5 support. That is a compatibility/maintenance bump, not a feature release. It confirms the maintainer is responsive to framework-version issues, but it also means the declared support ceiling is Symfony 5 — relevant if your roadmap targets Symfony 6.x or 7.x.
• Upgrade-path input: If a Symfony 4.4 → 5.x migration is on the roadmap, this release removes one blocker for teams already using the bundle. If you are past 5.x, this release does not help you and the package should be flagged as a migration liability.

When to Consider This Package

Consider it when:

• You are on a Symfony application (3.4 / 4.x / 5.x) and have a genuine repeated-route-parameter problem — locale-aware or tenant-aware URL generation appearing in many templates and controllers.
• You want the behavior as a declarative bundle convention rather than a bespoke listener each team re-implements.
• You are comfortable pinning to a pre-1.0 (0.1.x) dependency and can absorb breaking changes on minor version bumps under semver's 0.x rules.
• You have verified test coverage and recent commit activity beyond the single compatibility PR in this release.

Look elsewhere when:

• You are building on Laravel. Use framework-native facilities (e.g. URL::defaults()) — this bundle does not apply, and forcing a Symfony bundle into a Laravel codebase is a non-starter.
• You target Symfony 6.x or 7.x. No declared support in this release; adopting now likely means maintaining a fork of the compatibility shim.
• You require a stable 1.0+ API contract or a formal security/deprecation policy. A 0.1.x package with a single contributor-driven compat PR does not provide that assurance.
• Your need is a five-line request listener. The dependency is not earning its keep; the supply-chain and upgrade-review overhead exceeds the code it saves.
• The parameter set is dynamic or per-route conditional. Autofill conventions tend to get awkward once rules diverge; explicit parameter passing is clearer and easier to test.

Release-specific read on v0.1.2: The only change is Symfony 5 support (contributed by sstok, issue #5). This is a low-risk, low-urgency update. It improves the package's viability for Symfony 5 adopters and slightly improves the maintenance signal, but it does not change the underlying build-vs-buy calculus and does not expand supported frameworks beyond Symfony 5.

How to Pitch It (Stakeholders)

For executives (one paragraph): We evaluated rollerworks/route-autofill-bundle, an open-source Symfony add-on that removes repetitive code when generating links that must carry context such as language or tenant. The newest release, v0.1.2, is a small maintenance update that adds support for Symfony 5 — it does not add new capabilities. Our recommendation is low priority, no action required now: the package is pre-1.0, the functionality is inexpensive to build ourselves, and it is not usable in our Laravel-based services. It is worth a look only if we commit to a Symfony 3.4/4.x/5.x application and want the convention for free.

For engineering (summary):

• What changed: v0.1.2 adds Symfony 5 compatibility (PR #5, contributed by sstok). No API changes, no deprecations, no new features, no breaking changes relative to prior 0.1.x releases.
• Risk profile: Pre-1.0 (0.1.x) — treat minor bumps as potentially breaking. Low bus factor. Verify CI matrix and test coverage before pinning; a single compat PR is a positive maintenance signal but not proof of ongoing support.
• Do not adopt if: the codebase is Laravel, or the target runtime is Symfony 6+. In both cases the bundle is out of scope today.
• If we adopt: pin an exact version, wrap the behavior behind our own route-generation helper so the dependency is swappable, and add a Symfony-upgrade test so the eventual 6.x/7.x move surfaces the gap early rather than at migration time.
• Effort if we build instead: roughly half a day for a request-scoped listener covering the common parameter-persistence case — worth doing if we only need one or two sticky parameters.