Skip to content

[input-group] - inconsistent Variable Naming Between Schema and Exposed Component Variables In the schema #15780

@desig9stein

Description

@desig9stein

Since the schema variables are not exposed to the end user, anyone trying to create a custom theme using the schema variable names (e.g., search-resting-elevation) will encounter errors. On the other hand, using the exposed variables (e.g., search-resting-shadow) currently has no effect, which leads to confusion and failed customizations.

Schema props

search-resting-elevation,
search-hover-elevation,
search-disabled-elevation,

However, in the component we expose to the end user:

search-resting-shadow,
search-hover-shadow,
search-disabled-shadow,

Suggested Solution
We should migrate the variable to align with the schema by renaming:

search-resting-shadow → search-resting-elevation
search-hover-shadow → search-hover-elevation
search-disabled-shadow → search-disabled-elevation

This would ensure consistency between the schema and the exposed variables and allow users to customize reliably.

Metadata

Metadata

Assignees

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions