feat: create model for adding appearances to components

[KingOfTac]

Feature Request

Expected Behavior

Current Behavior

Possible Solution

Context

Examples

[bheston]

I've come across another place I'd like to use this model, which is that some components have different presentations. For instance, a component often referred to as a "segmented control" is, from an ARIA perspective, either a radiogroup or tablist. I'd like to use Adaptive UI to configure that presentation based on an attribute.

I realize with the model we're considering building we're not locked into the word "appearance", but I think "variant" may be a stronger default. To me it implies any difference that might not be strictly appearance related, and it better defines even a semantic name like "primary" or "secondary" because that's more about the function, which happens to have a different appearance often.

That said, I'm hoping we can work on this soon 😬

[KingOfTac]

I've come across another place I'd like to use this model, which is that some components have different presentations. For instance, a component often referred to as a "segmented control" is, from an ARIA perspective, either a radiogroup or tablist. I'd like to use Adaptive UI to configure that presentation based on an attribute.

I realize with the model we're considering building we're not locked into the word "appearance", but I think "variant" may be a stronger default. To me it implies any difference that might not be strictly appearance related, and it better defines even a semantic name like "primary" or "secondary" because that's more about the function, which happens to have a different appearance often.

That said, I'm hoping we can work on this soon 😬

Agree with using variant over appearance. What would be an example of a segmented control?