feat(tags input): export type InputValueChangeDetails #3577
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.
Tags Input — export type InputValueChangeDetails
Problem
Ark-UI tags-input exports type
ValueChangeDetails
but notInputValueChangeDetails
, which creates an inconsistency in the API. Both types are available from the underlying@zag-js/tags-input
package:Use Case
This export is needed for proper type safety when handling input value changes in current components. ie
useTags
component needs to handle both value changes and input value changes:Changes
InputValueChangeDetails
to the exports inpackages/react/src/components/tags-input/tags-input.ts
Why
This type was available from
@zag-js/tags-input
but not exported, making it unavailable to users of the library who need to properly type their input value change handlers.Testing
The change is minimal and only adds an export for an existing type that was already available from the underlying package. No breaking changes or new functionality is introduced.
Related
This addresses the inconsistency where
ValueChangeDetails
is exported butInputValueChangeDetails
was not, despite both being available from the same source package.