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
{{ message }}
This repository was archived by the owner on Mar 16, 2023. It is now read-only.
Hi @bbigras, Since qwik has changed its API so much since this project started, i was waiting for the new server actions API to be released.
Since then Ive learnt that getting Urql working with Qwik means we have to sacrifice a bunch of great functionality from both Qwik and Urql. They actually solve the same problems.
Using graphql with Qwik should be done as once off requests in an onGet, loader$, or action$. And you should then make use of native Qwik elements to handle prefetching, state, and reactivity.
I havent reach this point yet in my own project as Im first rolling out our static pages, but when I get to it I'll look into a new way to integrate graphql with just loaders, actions, and endpoints, making most of this project redundant.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
To reproduce:
git clone https://github.com/bbigras/test-qwik-urql.git cd test-qwik-urql npm install npm run preview
Btw, with
npm run dev
the code works and fetches data from a public star wars api at https://swapi-graphql.netlify.app/.netlify/functions/indexnpm: '9.3.1',
node: '18.14.0',
The text was updated successfully, but these errors were encountered: