2.0.0 Alpha prep #2887
Merged
2.0.0 Alpha prep #2887
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This ensures all imported types are using the `type` keyword.
Will be used in the new and existing components.
Right now Next.js does barrel file optimization and re-writing imports
to a real path in the `dist` folder. Most of those rewrites don't
actually exist because they have an assumption:
```js
import { FooBar } from '@headlessui/react'
```
is rewritten as:
```js
import { FooBar } from '@headlessui/react/dist/components/foo-bar/foo-bar'
```
This script will make sure these paths exist...
This hook has a default implementation when comparing objects. If the object contains an `id`, then we will compare the objects by their `id`'s without the user of the library needing to specify `by="id"`. If the objects don't have an `id` prop, then the default is still to compare by reference (unless specicified otherwise).
…(singular) This is so that we can be consistent with the other components.
This is a more complex version of a soon to be exported `mergeProps` that we will be using in our components.
These are the ones being exposed inside `data-headlessui-state="..."`
RobinMalfait
force-pushed
the
feat/catalyst
branch
from
f0af3a9 to
cd9749e
Compare
RobinMalfait
force-pushed
the
feat/catalyst
branch
from
cd9749e to
b14e756
Compare
These playgrounds are mainly test playgrounds. Lower priority for now, we will get back to them.
RobinMalfait
force-pushed
the
feat/catalyst
branch
from
b14e756 to
20165b4
Compare
|
@RobinMalfait Love where this update is going and understand that it supports the new Catalyst toolkit, which is react-only. Do you plan at any point to add Vue support for these new Headless UI components in future updates, or is it reasonable to expect that the updates in this 2.0.0 alpha and future releases will only go to the React components? |
|
Just saw this note in the release announcement:
Glad to hear it! |
This was referenced May 28, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR includes a bunch of fixes and new components / feautures such as:
Added
CheckboxcomponentRadiocomponent as an alternative to the existingRadioGroup.OptioncomponentButtoncomponentInputcomponentTextareacomponentSelectcomponentField,Label,Description,FieldsetandLegendcomponentsDataInteractivecomponentanchorandmodalprop toComboboxOptions,ListboxOptions,MenuItemsandPopoverPanelcomponentsListboxSelectedOptioncomponentMenuSection,MenuHeading, andMenuSeparatorcomponentsdata-*attributes as an alternative to the existingdata-headlessui-state="..."attributeautoFocusprop on focusable components (which maps todata-autofocus)Changed
data-autofocusin the dialog)activeprop in favor of thefocusprop on theComboboxOption,ListboxOption,ListboxOption,MenuItem,MenuItem,RadioOption, andRadioOptioncomponentsFixed