Reflect Vue 3 + Vuetify 3 / adapter layer in description and README#3
Merged
Conversation
The framework-adapter layer (PR #2) shipped first-class Vue 3 + Vuetify 3 support, but the package description and the README ecosystem diagram still read React/Tailwind-only. Align both with the current two-adapter reality (React + Tailwind/shadcn, Vue 3 + Vuetify 3) without overstating scope. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Updates repository metadata to accurately reflect existing multi-framework support (React + Tailwind/shadcn and Vue 3 + Vuetify 3) via the framework-adapter layer introduced previously, ensuring externally visible descriptions are no longer React-only.
Changes:
- Update
package.jsondescription to mention component codebases and both supported framework stacks. - Update the README ecosystem diagram label from “your React/Tailwind codebase” to “your component codebase”.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| README.md | Renames the ecosystem diagram’s input label to be framework-agnostic. |
| package.json | Expands the package description to reflect React + Vue support via the adapter layer. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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.
What
Two text-only edits so the repo's own metadata matches what
mainalready ships:package.jsondescription— was "React + Tailwind/shadcn codebases" only; now "component codebases (React + Tailwind/shadcn, Vue 3 + Vuetify 3) through a framework-adapter layer."README.mdecosystem diagram — top lineyour React/Tailwind codebase→your component codebase.Why
PR #2 added the framework-adapter layer with first-class Vue 3 + Vuetify 3, but these two surfaces still read React-only. This was caught during a content audit reconciling aesthetic-function.com copy with the repo. The README prose, handbook, and adapter docs already describe both frameworks; this just closes the last two React-only strings. No code, scope, or version change (still
0.1.0-alpha.1, experimental).npm run buildpasses.🤖 Generated with Claude Code