Nova Havingable Laravel Package

Product Decisions This Supports

• Niche capability evaluation: webard/nova-havingable is an early-stage (v1.0.0) package aimed at Laravel Nova admin panels, apparently adding HAVING-clause support so resources can be filtered/sorted on aggregated columns (e.g. counts, sums) in Nova's index. This supports a build-vs-buy decision for teams whose internal tooling needs aggregate-based filtering without forking Nova or writing custom query hooks.
• Roadmap input for internal admin tooling: If your roadmap includes richer Nova dashboards or operational screens where "show me records where related_count > N" is a common need, this package is a candidate to unblock that work cheaply.
• Scope check, not a platform bet: Because this is an initial release by an individual/small maintainer with no track record yet, it should be treated as a tactical dependency rather than a strategic one. It informs decisions like "can we ship aggregate filtering this sprint?" but should not drive architecture.
• Use cases: Order/customer screens filtering on line-item totals, support queues filtering on ticket counts, inventory views filtering on stock aggregates — anything Nova-native that currently requires exporting to a spreadsheet or a custom controller.

When to Consider This Package

• Consider it when: you are already on Laravel Nova, your team is comfortable with Nova's query customization, and you have a concrete feature that needs HAVING-level filtering on aggregates. At v1.0.0 the surface area is small enough to vendor or audit quickly.
• Evaluate first: read the source (it is one initial commit) and confirm it matches your Nova major version — Nova's internals change between majors, and a fresh 1.0.0 has not yet proven version-tracking. Check issue/PR activity and whether the maintainer responds.
• Look elsewhere when: you need Nova alternatives (Filament, custom Livewire tables) — most modern admin frameworks support aggregate filtering natively; when you cannot tolerate a single-maintainer dependency in a critical path; when your aggregate needs are complex enough that raw query scopes or a custom Nova filter would be clearer and better tested; or when your Laravel/Nova versions are not explicitly supported.
• Fallback plan: be prepared to inline the trait into your codebase. Its likely small footprint makes the exit cost low, which is the main reason adoption is defensible at this stage.

How to Pitch It (Stakeholders)

To executives: A small, low-cost open-source add-on for our Nova admin panel that lets internal teams filter and sort records by totals and counts (e.g. customers by order volume) directly in the admin UI. It removes a class of manual spreadsheet work. Risk is contained: it's tiny, free, and can be replaced by in-house code if the maintainer stops supporting it. Recommended as a scoped pilot, not a platform commitment.

To engineering: webard/nova-havingable v1.0.0 is an initial release adding HAVING support to Nova resource queries. It is early — one commit, unproven maintenance, no version-compatibility matrix yet. Proposal: spike it against our Nova version, review the source, and either adopt with the trait vendored into our repo or replicate it in-house if the audit surfaces concerns. Do not treat it as a long-term dependency until it has a release history.