FWIW, I think this would be even more valuable if this style testing can expand into domain-specific components. It would be a win if we have tests that will fail when a token is updated and causes a domain-specific component's computed value to change in a way that causes an accessibility issue.
Bug 1952294 Comment 1 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
FWIW, I think this would be even more valuable if this style testing can expand into domain-specific components. It would be a win if we have tests that will fail when a token update causes a domain-specific component's computed value to change in a way that causes an accessibility issue.
FWIW, I think this would be even more valuable if this style testing can expand across consumer usage. For instance, it would be a win if we have tests that will fail when a token update causes a consumer's component to change in a way that causes an accessibility issue.
FWIW, I think this would be even more valuable if this style testing can expand across consumer usage. For instance, it would be a win if we have tests that will raise when a token update causes a consumer's component to change in a way that causes an accessibility issue.