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
In the refactor I started to clean things up one of the things we are doing is getting rid of URQL client. Today we have a non-traditional usage of URQL client when we are utilizing it for the API layer to serve. We export a client instance and share it in both indexer-agent and indexer-cli. There is no real GraphQL validation happening today and I found inconsistencies in the API which are not being caught.
The goal with this task is to refactor to use graphql-yoga and then tests utilities will be updated to use @graphql-tools/executor-http (see yoga docs here on testing)
I am hoping that cleaning up the URQL setup cause GraphQL client we fix our memory issues cause one of the known issues on URQL which feels like what we are seeing in #41 cause we are using the version of URQL which is suspected to have leaks.
The text was updated successfully, but these errors were encountered:
In the refactor I started to clean things up one of the things we are doing is getting rid of URQL client. Today we have a non-traditional usage of URQL client when we are utilizing it for the API layer to serve. We export a client instance and share it in both
indexer-agent
andindexer-cli
. There is no real GraphQL validation happening today and I found inconsistencies in the API which are not being caught.The goal with this task is to refactor to use
graphql-yoga
and then tests utilities will be updated to use@graphql-tools/executor-http
(see yoga docs here on testing)I am hoping that cleaning up the URQL setup cause GraphQL client we fix our memory issues cause one of the known issues on URQL which feels like what we are seeing in #41 cause we are using the version of URQL which is suspected to have leaks.
The text was updated successfully, but these errors were encountered: