Nathan Burgess
Nathan Burgess
In case anyone else comes across this thread: you can simply access `error.graphQLErrors` now. ```javascript const { error } = useQuery(SOME_QUERY) if (error) console.log(error.graphQLErrors) ```
> @nathanburgess While correct you can access it via the errors, the problem is accessing the extensions when there _isn't_ an error. Ah, my bad, I misinterpreted the issue then.
Are there any plans to fix this? This is a pretty common scenario that's widely supported in databases, it makes sense that Prisma could handle it as well.
> wth when will this feature be implemented working on a production-ready app and the deadline is next months! Maybe don't use something that lacks a feature you need in...
I would also love to see this implemented