Query Filter Bundle Laravel Package

Product Decisions This Supports

• Build vs. buy for query filtering: This package (a Symfony *-bundle, not a Laravel-native package) provides query-parameter–based filtering of collections/entities. The decision it informs is whether to adopt an off-the-shelf filtering layer or build a thin, framework-idiomatic filter (e.g., a Laravel query-scope/request-filter) in-house. Given the Laravel framing, "build" is the lower-risk path; "buy/adopt" only makes sense if the team is actually on Symfony.
• Dependency/maintenance posture: The fix-deps release is not an upstream feature release — it is a branch pinned to a personal fork (github.com/glebkaf/query-filter-bundle) that strips the sensio/extra-bundle dependency. This is a supply-chain and long-term-maintenance signal, not a capability signal. PM should record it as a risk, not a roadmap enabler.
• Upgrade-friction reduction: Dropping the deprecated sensio/extra-bundle dependency lowers Symfony upgrade friction for teams already using this bundle. This supports a "keep the lights on" decision, not a new-feature bet.
• Roadmap impact: None material. fix-deps adds no user-facing capability, no API changes, and no new use cases. It should not move prioritization.

When to Consider This Package

Consider it when:

• The project is Symfony-based (the package is a bundle and historically ties into the Symfony bundle ecosystem), not Laravel.
• You need lightweight, declarative query-parameter filtering and want to avoid writing it yourself.
• You are comfortable pinning to a non-official fork via a vcs repository and accept the reproducibility/maintenance trade-off (the fix-deps alias is a branch, not a semver tag).

Look elsewhere (or build in-house) when:

• The stack is Laravel — the bundle model and sensio heritage don't map cleanly; a native request-filter/query-scope is simpler and better supported.
• Your policy forbids depending on personal forks or unversioned branch aliases (CI reproducibility, security review, SBOM requirements).
• You need a maintained, officially released dependency line with a clear changelog and support commitment.

How to Pitch It (Stakeholders)

Executive summary: This release is a dependency-cleanup fix, not a feature. It removes reliance on the deprecated Symfony sensio/extra-bundle by publishing a fix-deps branch from a personal fork. The package is a Symfony bundle (query-filter-bundle), so it is not a natural fit for a Laravel codebase — for Laravel work, the recommendation is to build a small native filter rather than adopt this.

For engineering: The fix-deps branch eliminates a deprecated dependency, which is a modest maintenance win — but it arrives via a forked vcs repository and a branch alias rather than a tagged release. That introduces reproducibility and supply-chain review overhead. Treat adoption as an explicit risk decision; if used, pin to a commit SHA and track the fork's provenance.

Bottom line for roadmap: No user-facing value, no prioritization change. Use it only to reduce Symfony upgrade friction, and only where a fork dependency is acceptable. For Laravel, recommend build-in-house.