Redux Toolkit createSlice name uniqueness: missing global constraint

Goal

In a large application, each feature defines a Redux Toolkit slice with a name that prefixes all generated action types. The intent is to isolate actions by feature, but the Toolkit does not enforce that these names are globally unique.

Uncertainty

When two slices share the same name, their action type strings collide (e.g., counter/increment from both slices). This can cause both reducers to run for a single dispatched action, leading to unpredictable state updates. There is no runtime or compile‑time safeguard to detect or prevent such collisions.

Questions

• What mechanisms can enforce global uniqueness of createSlice names across a codebase?
• Can a lint rule or build‑time check reliably detect duplicate slice names before the application runs?
• Does changing a slice name retroactively alter existing action type strings in a way that breaks middleware or persisted logs?