You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The usage of useRouteBaseName differs from the other composables as it doesn't return a function to get the route base name, but directly returns the route base name. This won't work in all situations as it calls useRoute and useRouter every time, which must only be called in setup, a plugin or route middleware.
I will look into making a PR to make useRouteBaseName consistent with the other composables, please let me know if this difference in behaviour is intentional and should not be changed.
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered:
Environment
Darwin
v16.14.2
3.2.0
2.2.1
[email protected]
vite
srcDir
,app
,dir
,alias
,typescript
,runtimeConfig
,vite
,modules
,googleFonts
,intercom
,i18n
,sitemap
,build
@pinia/[email protected]
,@nuxtjs/[email protected]
,@nuxtjs/[email protected]
,~/modules/nuxt-sitemap/module
,@nuxtjs/[email protected]
,@nuxt/[email protected]
,~/modules/nuxt-intercom/module
,~/modules/nuxt-stripe-module/module
,@kevinmarrec/[email protected]
-
Reproduction
N/A
Describe the bug
The usage of
useRouteBaseName
differs from the other composables as it doesn't return a function to get the route base name, but directly returns the route base name. This won't work in all situations as it callsuseRoute
anduseRouter
every time, which must only be called insetup
, a plugin or route middleware.I will look into making a PR to make
useRouteBaseName
consistent with the other composables, please let me know if this difference in behaviour is intentional and should not be changed.Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: