feat(textarea): add textarea input component #264
Merged
Conversation
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
Contributor
|
@MattA-Official is attempting to deploy a commit to the Nuxt Team on Vercel. A member of the Team first needs to authorize it. |
7 tasks
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
commit: |
larbish
approved these changes
Jan 13, 2026
Contributor
larbish
left a comment
larbish
left a comment
There was a problem hiding this comment.
Thanks 💚 !
I did update Nuxt Content to fix the type issue, might be fixed once nuxt/content#3687 is merged.
I've only added small changes related to the refactor I've done in my latest PR: #257
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Resolves #232
This PR introduces a dedicated multi-line
textareainput component to the Studio, as requested in #232Upstream Dependency (@nuxt/content) While this feature works functionally within Studio, using it in content.config.ts triggers a TypeScript error because the @nuxt/content schema definition does not yet recognise 'textarea' as a valid value for
.editor({input: '...'}).