-
Notifications
You must be signed in to change notification settings - Fork 306
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
Labels
Comments
Closed
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 :)) |
I am closing this as I believe I have a satisfactory solution designed here, I just need to implement it now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 forexpired-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 !
The text was updated successfully, but these errors were encountered: