Tags For Laravel Laravel Package

Product Decisions This Supports

• Multi-tenant and soft-delete correctness: Release 1.0.2 fixes GET tags/{type}/popular?on= so counts respect the model’s global scopes. This directly supports product decisions about exposing popularity/trending tag data in tenant-scoped or soft-deleted environments without leaking counts across tenants or including deleted records.
• Feature scope for tagging/trending surfaces: PMs can confidently include “popular tags” in admin dashboards, discovery pages, reporting, or search facets, knowing the package now honors Laravel’s global scope conventions rather than bypassing them.
• Build vs. buy: For teams already on Laravel, this package reduces custom work for tag popularity endpoints, scoped queries, and tenant-aware counting. The fix lowers the need to fork or wrap the endpoint for compliance-sensitive isolation.
• Roadmap sequencing: Treat this as a reliability/compliance fix rather than a headline feature. It unblocks shipping popularity-based UX in multi-tenant or soft-delete-heavy products, but it does not change the package’s core capabilities.
• Risk reduction for regulated or B2B products: Because the fix prevents other-tenant and soft-deleted records from inflating popular-tag counts, it supports data-isolation expectations in B2B, enterprise, and privacy-sensitive products.

When to Consider This Package

Consider adopting this package when:

• You are building on Laravel and need tag management with queryable “popular tags” behavior without writing your own aggregation endpoint.
• Your application uses global scopes for tenant isolation, soft deletes, publication status, or similar access controls, and you expect package endpoints to honor those scopes.
• You want a small, focused tagging package rather than a full taxonomy/content-classification system.
• You need to ship discovery, filtering, or reporting features where tag popularity is derived from scoped application data.
• You are evaluating a low-friction dependency and can accept that the package’s behavior is tied to Laravel’s Eloquent/global-scope conventions.

Look elsewhere or plan custom work when:

• You need advanced taxonomy features such as hierarchical categories, translations, synonym management, editorial curation, or ML-based classification.
• Your product requires explicit, documented SLA/security guarantees beyond open-source package maintenance.
• You cannot rely on Laravel global scopes as the source of truth for tenant isolation and instead need database-level row security or separate schemas.
• You need popularity counts computed from analytics/event streams rather than transactional Eloquent records.
• You require a vendor-supported package with formal support contracts.

How to Pitch It (Stakeholders)

For executives: This release is a correctness and trust fix for tag popularity data. It ensures popular-tag counts only include records the application is allowed to see, excluding soft-deleted and other-tenant records. That reduces the risk of leaking tenant activity or reporting inflated engagement in multi-tenant and compliance-sensitive products. It is not a new feature, but it makes existing tagging/discovery functionality safer to ship.

For engineering: Version 1.0.2 fixes the GET tags/{type}/popular?on= endpoint to respect the model’s global scopes when counting records. This aligns package behavior with Laravel’s scoping model, including soft deletes and tenant constraints. Engineering should verify that relevant models define global scopes correctly, add regression tests for tenant/soft-delete popularity counts, and avoid bypassing scopes unless intentionally required. No breaking API change is indicated.