Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@ivanmaxlogiudice
Copy link
Contributor

@ivanmaxlogiudice ivanmaxlogiudice commented Sep 28, 2025

πŸ”— Linked issue

❓ 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

This happens with the vue version.
The first problem is that the useCookie stub doesnt get the value like in Nuxt (with a default function)

const value = ref(_options?.default?.() ?? null) as Ref<T>

The second problem is that in its use, the value its in a depeer level, we have to use .value.value to get the actual value instead of .value

πŸ“ Checklist

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

@benjamincanac benjamincanac changed the title fix(vue): stub useCookie compatiliity with nuxt fix(vue): align useCookie stub with nuxt's default value handling Sep 29, 2025
@pkg-pr-new
Copy link

pkg-pr-new bot commented Sep 29, 2025

npm i https://pkg.pr.new/@nuxt/ui@5089

commit: 6b916db

Copy link
Member

@benjamincanac benjamincanac left a comment

Choose a reason for hiding this comment

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

Thanks 😊
I've updated the snapshots and applied the same changes to the inertia stubs!

@benjamincanac benjamincanac merged commit f531807 into nuxt:v4 Sep 29, 2025
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

v4 #4488

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants