Seed Token Cascade Limits in Alias Overrides

Short answer

Yes — an explicit Alias token override replaces the derived value for that token and stops further automatic derivation from the Seed token for that specific alias. The override wins and the token becomes static until you remove it or pass a new token prop.

Precedence is: component-level token props > ConfigProvider theme.token overrides > Seed-derived Map/Alias values. A Seed update only affects alias tokens that are not overridden at a higher level.

What actually happens

Ant Design 5 generates Map and Alias tokens from Seed tokens using a fixed algorithm. When you override an Alias token (e.g., colorPrimary), the engine bypasses the algorithm for that token. The Seed token still drives Map and Alias tokens, but the overridden alias is no longer linked to the Seed token.

So if you change the Seed token at runtime, the overridden Alias token stays constant. The component's hover and active states are derived from the Seed token, not the overridden Alias token. If you override colorPrimary, the hover/active colors are still derived from the Seed token, not from the overridden Alias token.

Verification

Render a Button with a Seed token (e.g., colorPrimary) set via ConfigProvider, then pass a token prop that overrides its colorPrimary Alias. Inspect the computed style for the button's background and its hover/active states before and after changing the Seed token. Use React DevTools to toggle the ConfigProvider theme.token Seed value and observe whether the overridden Alias token's value changes. If it stays constant, derivation is disabled for that token.

Recommended pattern

To keep derived states (hover, active) in sync, either avoid overriding individual Alias tokens and instead modify the Seed token or the theme algorithm, or when a component-specific Alias must be overridden, also provide matching overrides for the related state tokens (e.g., colorPrimaryHover, colorPrimaryActive) using the same token object.

Caution

Overriding Alias tokens can break automatic dark-mode generation and accessibility contrast guarantees because the derived hover/active colors are no longer linked to the Seed token. If you rely on runtime theme switching, failing to update component-level token overrides when the Seed changes will produce visual inconsistencies where overridden colors stay static while the rest of the theme shifts.