benjamincanac ยท GitHub

@kleenkanteen

Copy link Copy Markdown

Contributor

I lost 2h because the docs were incorrect. It also caused incorrect AI explanation across multiple LLMs.

โ“ Type of change

  • ๐Ÿ“– Documentation (updates to the documentation or readme)
  • ๐Ÿž Bug fix (a non-breaking change that fixes an issue)
  • ๐Ÿ‘Œ Enhancement (improving an existing functionality)
  • โœจ New feature (a non-breaking change that adds functionality)
  • ๐Ÿงน Chore (updates to the build process or auxiliary tools and libraries)
  • โš ๏ธ Breaking change (fix or feature that would cause existing functionality to change)

๐Ÿ“š Description

  1. The previous explanation incorrectly wrote that the index of the tab matters, when that isn't the case.

๐Ÿ“ Checklist

  • I have linked an issue or discussion.
  • I have updated the documentation accordingly.

@kleenkanteen

@pkg-pr-new

Copy link Copy Markdown
npm i https://pkg.pr.new/@nuxt/ui@5722

commit: 4e2ba60

@vercel

benjamincanac

@kleenkanteen

@vercel

@benjamincanac benjamincanac changed the title docs(tabs): fix explanation for setting active tab docs(tabs): improve model value examples

Dec 21, 2025

@benjamincanac

benjamincanac

Copy link Copy Markdown

Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've updated the docs to split into two sections, let me know what you think!

@vercel

@kleenkanteen

Copy link Copy Markdown

Contributor Author

looks good.

I was hoping to add a simple example of how setting the default item works, but I guess it's not necesary since the part about the value property controlling it was fixed and added since the last time I looked at it.

@benjamincanac

benjamincanac

@vercel

@benjamincanac

Read the original on github.com โ†—