Sylius Location Bundle Laravel Package

Product Decisions This Supports

• Feature: SEO-friendly URLs on custom/extended entities. This release is a targeted fix for slug generation failing when Gedmo's Sluggable listener runs against an entity that extends a Sylius Resource Bundle base entity. If your roadmap includes custom product, taxon, or CMS-page entities with human-readable URLs, this is the piece that unblocks it.
• Build vs buy. The capability is narrow and well-understood. Adopting costs a single Composer dependency plus pinning discipline; building means reimplementing listener wiring and re-solving the extended-entity edge case ourselves. On effort alone, adopting wins — but see the risk framing below, because "cheap to adopt" is not "cheap to own."
• Platform upgrade sequencing. v0.4.1 is tagged against Sylius v1.0.0-beta.1. That makes this package a companion dependency to a larger platform upgrade decision: we can't adopt it independently of our Sylius version, so it belongs in the upgrade epic, not in a feature backlog.
• Use cases to validate against: multi-store catalogs where slugs must be unique per channel; migrations of legacy slugs onto newly extended entities; any resource where the slug field lives on a subclass rather than the mapped base class.
• Roadmap caution. At v0.4.x with beta-aligned releases, this package's API stability mirrors Sylius beta stability. Do not schedule dependent features against a GA date until the underlying platform reaches one.

When to Consider This Package

Adopt when all of the following hold:

• You are on Sylius (or Symfony with Sylius Resource Bundle) and use Gedmo Sluggable on an entity that extends a base resource entity — the exact configuration this patch addresses.
• You are already committed to, or actively evaluating, Sylius 1.0.0-beta.1. The release is explicitly scoped to that beta, so it is not a safe bet on older or newer lines without verification.
• The dependency can be contained: pinned in Composer, wrapped behind an internal slug service, and forked if abandoned. Its surface area is small enough that a fork is realistic.
• You can absorb pre-1.0 churn — expect breaking changes on minor version bumps under semver's 0.x rules.

Look elsewhere when:

• Your stack is Laravel, not Symfony/Sylius. There is no Sylius Resource Bundle to integrate with. Use spatie/laravel-sluggable or a Str::slug + model-event approach instead; this package solves a problem you do not have.
• You already place the slug field on the mapped base entity rather than a subclass. The bug this release fixes does not apply, and plain Gedmo Sluggable is sufficient.
• You require >=1.0 API guarantees, a published support window, or a security-response commitment. None of those are evident here.
• You are not tracking the Sylius beta and cannot tolerate a dependency whose release cadence is coupled to someone else's prerelease cycle.

Release signal assessment: v0.4.1 is a patch-level bugfix with no new features, no deprecations, and no breaking changes. The meaningful information is the coupling — it names Sylius 1.0.0-beta.1 as its target, which tells us more about maintenance posture than the fix itself. Treat this as evidence the package is actively maintained against the beta, not as evidence it is production-ready.

How to Pitch It (Stakeholders)

For executives (one paragraph): This is a small integration package that fixes URL slug generation for custom content and catalog entities on our platform. It is inexpensive to adopt and removes a concrete blocker on SEO-relevant features. The risk is maturity, not cost: the package is pre-1.0 and its releases are tied to a beta version of the underlying platform. Our recommendation is to adopt it narrowly — pinned, wrapped behind an internal interface, with a documented fork path — and to hold any customer-facing commitment until the platform itself reaches general availability.

For engineering (one paragraph): The v0.4.1 change circumvents a failure mode where the Gedmo Sluggable listener does not behave correctly against an entity that extends a Sylius Resource Bundle base entity. Scope is a single patch against Sylius 1.0.0-beta.1, with no API changes. Pin to v0.4.1 exactly, verify the fix against our own extended-entity configuration rather than trusting the changelog, and add a regression test covering slug uniqueness on the extended entity so a future bump cannot silently reintroduce the failure. Keep the dependency behind a single slug service — no direct calls from controllers or templates — so that replacing it with an in-house listener or a fork is a one-file change.