Bruno Laravel Package

Product Decisions This Supports

• API and resource roadmap: The 1.1.0 release adds filtering support within relationships, which can enable nested-resource API use cases such as filtering parent records by related-record attributes. This is a meaningful capability for products exposing searchable, filterable REST APIs.
• Build vs. buy: If the product needs declarative Eloquent filtering, especially across relationships, this package becomes a stronger candidate to adopt instead of maintaining a bespoke filter layer.
• Feature prioritization: Relationship filtering can unlock admin dashboards, reporting views, search/filter UX, and partner integrations that previously required custom query code. Validate customer demand before making it a roadmap dependency.
• Risk and release planning: The release is additive and appears non-breaking based on the notes. Treat 1.1.0 as a low-risk feature increment, but verify documentation, tests, authorization patterns, and query-performance implications before broad adoption.

When to Consider This Package

• Consider it when the team uses Laravel/Eloquent and needs consistent, allow-listed filtering, including filters against related models.
• Consider it for internal admin tools, APIs, dashboards, or reporting endpoints where relationship-aware filtering reduces custom query-builder code.
• Consider a pilot when the team wants a small package rather than building and maintaining its own filtering abstraction.
• Look elsewhere if the product needs a full query language, advanced full-text search, GraphQL-style relation traversal, complex aggregations, or enterprise-grade support/SLAs.
• Look elsewhere if relationship-filter semantics are undocumented, untested for authorization scoping, or likely to create N+1/performance issues in high-traffic paths.
• Be cautious if the roadmap requires long-term LTS guarantees; a 1.x package with sparse release notes should be evaluated with a spike and test coverage.

How to Pitch It (Stakeholders)

Executive summary: This package’s 1.1.0 release adds relationship filtering, extending its usefulness for APIs and admin/reporting experiences that need to filter records by related data. The change appears additive and non-breaking, making it a reasonable candidate for a scoped pilot rather than a risky migration. The product value is reduced custom query code and faster delivery of nested filtering use cases; the main diligence items are documentation, authorization scoping, and query performance. Engineering summary: validate the new relationship-filter behavior against representative Eloquent models, confirm allow-listing and authorization boundaries, add performance tests for nested filters, and adopt behind a feature flag or pilot endpoint before standardizing across the product.