Robin Malfait
a7e0f0a937
This PR simplifies the internal tests a bit. 1. Don't explicitly test if a component has a specific ID 1. Don't mock the `useId` hook if it's not necessary What we care about more is that 2 components (E.g.: `MenuButton` and `MenuItems`) are connected to each other. This is done via `id` and `aria-controls` attributes. The exact ID is not important. The main motivation for this is that every time we introduce some `useId()` hook call somewhere, the IDs will shift and it will look like some tests are broken. If we are not explicitly testing the IDs, we also don't really care about deterministic incrementing IDs in tests, so therefore we can remove some `useId` mocking. Note: some tests still have mocks like this (e.g.: `description.test.ts` & `label.test.ts`) but that's because they have some snapshot tests.
@headlessui/react
A set of completely unstyled, fully accessible UI components for React, designed to integrate beautifully with Tailwind CSS.
Installation
npm install @headlessui/react
Documentation
For full documentation, visit headlessui.dev.
Community
For help, discussion about best practices, or any other conversation that would benefit from being searchable:
For casual chit-chat with others using the library: