-
-
Notifications
You must be signed in to change notification settings - Fork 483
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG/FR with REPRO] APQ, handling correct GET requests with both Apollo and Urql #1085
Comments
@bbigras if you have some news, please help us! Thanks! 😃 |
This problem is due to |
Fixed in |
Wow. It was fast! Can you release so I can try it? Or how can I try the master branch? |
Yes,you can try it on master branch,I'll release it later.😄 |
I asked HOW I can try it. Not if. But I think I found how to. |
{
async-graphql = { git="https://github.com/async-graphql/async-graphql.git", branch="master" }
async-graphql-axum= { git="https://github.com/async-graphql/async-graphql.git", branch="master" }
} |
I tried. I get in my real project many errors. I'll try in the reproduction project right now. |
The reproduction repo works with master branch! Thank you very much! |
I look forward to a new release and now I am also trying to understand the problems I have on my real project with the master branch. |
Are you going to release soon? |
Hi guys!
I think this is the same problem that @bbigras had (but the Stale BOT closed it without a proper fix).
I created a small reproduction here: https://github.com/frederikhors/iss-async-graphql-apq-urql.git.
In it's README.md you can read:
To start
cargo run
cd web && npm install && npm run dev
Problem
If you open the browser (http://localhost:5000) in the console you can read the error:
The backend response is:
If I remove the line
persistedFetchExchange({ preferGetForPersistedQueries: true })
fromindex.svelte
it works (because it's using thePOST
method now and not the Automatic persisted queries anymore).Proposal
I think we should fix this because both Apollo & Urql (so the 90% of web projects) use the same API/functioning.
Practically today it is not possible to use this method with async-graphql at all.
Ref
Thank you very much for your work on this amazing project!
The text was updated successfully, but these errors were encountered: