Solucionando la re-autenticación/refresco de tokens en el cliente #33
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Agrega un link de manejo de errores de graphql, donde si detecta un error de autenticación, fuerza un refresco de la token de supabase.
Además, promueve los errores de graphql que encuentre a errores de JS. Cuando esto ocurre, las queries que causaron el error capturadas por el retry-link y reintentadas.
En ese momento, la token ya debería estar actualizada y la query pasar sin problemas :)
Dependemos de JSConfCL/gql_api#168
Caveats:
No he revisado otro tipo de errores de graphql. Por ahora, capturamos el auth, pero deberíamos revisar que otros errores no causen retries innecesarios.Fixed :)