docs: explain Tailwind styling in v1 - #454
Merged
TotomInc merged 1 commit intoAug 5, 2026
Merged
Conversation
TotomInc
self-requested a review
August 5, 2026 07:19
TotomInc
approved these changes
Aug 5, 2026
Owner
|
Thanks, that closes the documentation gap ! |
This file contains hidden or 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
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.
Summary
classesprop in v1Selectand unstyled primitivesMotivation
The migration guide currently covers the bundled stylesheet and data hooks, but it does not say what replaces the v0
classesprop. This leaves Tailwind users without a clear v1 path.Testing
pnpm --filter @vue3-select-component/docs lintpnpm --filter @vue3-select-component/docs exec nuxt preparegit diff --checkCloses #453