Route and Slug Collision Handling

Purpose

Use this page when an addon introduces or changes route paths, route keys, addon slugs, public target identifiers, or admin navigation targets.

Collision rule

Routes and slugs that affect runtime must be unique in their authority area. Do not accept a new route or slug if it would override an existing owner.

What to check

• Addon key uniqueness.
• Admin route keys and legacy views.
• Public route paths.
• Public target identifiers.
• Menu target provider identifiers.
• Table names and index names.
• Permission keys.

Handling a collision

Prefer changing the new addon or new route, not silently replacing an existing owner. If replacement is intentional, document it and migrate deliberately.

Slugs

Use central slug/key helpers. Do not hand-roll identity cleanup with ad hoc string replacement when the core identity helpers already exist.

Verification

After resolving a collision, verify both the new route and nearby existing routes still load.