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
TypeError: 'get' on proxy: property '0' is a read-only and non-configurable data property on the proxy target but the proxy did not return its actual value (expected '[object Object]' but got '[object Object]')
#548
Open
stack-vue opened this issue
Sep 11, 2023
· 0 comments
expecting the messages from Websocket. When i debugged, actually messages are coming but because of above error I am not able to capture the messages in my Vue file
Reproduction
No response
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered:
Environment
Darwin
v18.12.0
3.6.5
2.5.2
pnpm@8.6.10
vite
runtimeConfig
,app
,css
,imports
,modules
,apollo
,devtools
,build
,vite
,routeRules
,hooks
,sourcemap
@pinia-plugin-persistedstate/nuxt@1.1.1
,@pinia/nuxt@0.4.11
,@nuxtjs/i18n@8.0.0-beta.13
,@nuxtjs/apollo@5.0.0-alpha.6
-
Describe the bug
I am getting this error when I enable SubscribeToMore as below
const variables = ref({ where: { id: { _eq: props.instrument.id } } })
const res = ref(0)
const { subscribeToMore, onError: onFetchError, onResult: onFetchResult } = useQuery(query, variables)
onFetchResult((res) => {
res.value = res.data.records[0].value || 0
})
subscribeToMore({
document: subscriptionLtp,
variables: { where: { id: { eq: props.id } } },
updateQuery(, { subscriptionData }) {
console.log('------updateQuery-------')
res.value = subscriptionData.data.instruments[0].ltp || 0
},
})
onFetchError((error) => {
toast.error({ summary:
Error: ${error.message}
})})
Expected behaviour
expecting the messages from Websocket. When i debugged, actually messages are coming but because of above error I am not able to capture the messages in my Vue file
Reproduction
No response
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: