Seedy
Seedy
@seedy Handle the update either by listing tasks in issue description or pushing separate issues Then see if it can be handled quickly or not
Components already relying on the `as` behavior: - [x] `Badge` - [x] `Heading` ~~- [ ] `Box`~~ behavior makes sense ~~- [ ] `Text`~~ behavior makes sense - [x] `Button`...
Related issues: - https://github.com/traefik/faency/issues/351 - https://github.com/traefik/faency/issues/107
https://www.radix-ui.com/docs/primitives/components/select :tada:
@seedy Study value of integrating radix-ui 's component shortly
- We should test components not extending radix primitives - Testing accessibility is the most relevant part - Testing interactions with component - Avoid testing styles as it's redundant with...
We can have a story to describe the workaround as a "best practice" and see if we discover the reason behind this bug
Behaviour I would expect : screenshot of "Tab3" is a secondary button inactive, when it becomes active, it looks like other "Tab" buttons
@matthieuh FYI, I created an RFC issue here, so that we add eslint rules to Faency. I don't know if we require a discussion before implem, WDYT?
@paulocfjunior I'm on it