-
Notifications
You must be signed in to change notification settings - Fork 206
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
feat: Introduce GraphQLTokenFeeFetcher
(no traffic)
#736
feat: Introduce GraphQLTokenFeeFetcher
(no traffic)
#736
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's looking good overall, some minor comments :)
Pasting my comments from old PR. I think we want to shadow sample GQL traffic first, with FOT fee comparison. We aren't in rush to switch 10% (or whatever) traffic to GQL |
makes sense - I'll remove the traffic switch part from this PR and will add that logic to a different PR |
GraphQLTokenFeeFetcher
at 10% trafficGraphQLTokenFeeFetcher
(no traffic)
Graphite Automations"Request reviewers once CI passes on routing-api repo" took an action on this PR • (06/13/24)5 reviewers were added and 1 assignee was added to this PR based on 's automation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall LGTM
Introducing a
GraphQLTokenFeeFetcher
(implementation + tests only for now, no live traffic)This fetcher will use GraphQL endpoint to fetch token fee data, and will fallback to OnChain fetching if something goes wrong or to fetch any remaining tokens that couldn't be fetched from graphQL.
Did setup env variables
UNI_GRAPHQL_ENDPOINT
/UNI_GRAPHQL_HEADER_ORIGIN
for GraphQL in routing-apiA separate PR will follow for shadow traffic,
Testing