Skip to content
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

Possibility to catch errors on client level #235

Closed
d-ivashchuk opened this issue Dec 9, 2020 · 2 comments
Closed

Possibility to catch errors on client level #235

d-ivashchuk opened this issue Dec 9, 2020 · 2 comments

Comments

@d-ivashchuk
Copy link

I am looking for implementing a solution to enable refresh token workflow using graphlq-request. I can't see the possible way to catch the errors on the client, see what kind of error it is(looking for expired-token for example) and then execute mutation to get the new token and retry the first query that errored.

Did somebody implemented smth like this or maybe there is a native solution provided for the library which I don't see?

Thanks a lot !

@jasonkuhrt
Copy link
Owner

Been a while. This use-case will be considered for #853. Thanks for initially raising it @d-ivashchuk. Hope things are well! (Brief time as a Prisma colleague :))

@jasonkuhrt
Copy link
Owner

jasonkuhrt commented May 31, 2024

I am closing this as I believe I have a satisfactory solution designed here, I just need to implement it now.

#878 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants