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
After I update the deps using pnpm up -Lir, I got wrong type in data: const { data } = await useAsyncQuery<Query>()
vscode shows: const data: AsyncData<T, Error> rather than ListNotificationGqlResult(a type in Query)
so that I got wrong in const listNoteCountTypesCommentReply = computed(() =>listUnreadNotificationsCount.value.list.find(item => item.msgtype === 'comment_reply')?.count || 0)
for item gets any type
Expected behaviour
type of data mentioned above is ListNotificationGqlResult
Environment
Darwin
v20.15.0
3.12.4
3.12.0
2.9.7
[email protected]
-
features
,modules
,typescript
,imports
,appConfig
,app
,nitro
,apollo
,i18n
,vueuse
,unocss
,postcss
,headlessui
,compatibilityDate
@nuxtjs/[email protected]
,@nuxtjs/[email protected]
,@pinia/[email protected]
,@vueuse/[email protected]
,@unocss/[email protected]
,[email protected]
-
Describe the bug
After I update the deps using
pnpm up -Lir
, I got wrong type indata
:const { data } = await useAsyncQuery<Query>()
vscode shows:
const data: AsyncData<T, Error>
rather thanListNotificationGqlResult
(a type in Query)so that I got wrong in
const listNoteCountTypesCommentReply = computed(() =>listUnreadNotificationsCount.value.list.find(item => item.msgtype === 'comment_reply')?.count || 0)
for item gets
any
typeExpected behaviour
type of
data
mentioned above isListNotificationGqlResult
Reproduction
https://github.com/PatchyVideo/platinum/blob/nuxt/pages/notification.vue#L32 type of data cannot be infered as
ListNotificationGqlResult
while history version
https://github.com/PatchyVideo/platinum/blob/a29204bc08f402dff7f625802a8b51a3e651b34d/pages/notification.vue#L32 can infer it correctly
Additional context
plugin
GraphQL v0.1.2
andApollo GraphQL v1.20.0
is installed in my vscodeLogs
No response
The text was updated successfully, but these errors were encountered: