-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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: routing api integration #2116
Conversation
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/uniswap/uniswap-interface/EDnuTzCD3eV2NPkMJDq1qFpu4TGs |
return { | ||
tokenInAddress: tokenIn.wrapped.address, | ||
tokenInChainId: tokenIn.chainId, | ||
tokenOutAddress: tokenOut.wrapped.address, |
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.
hmm does the api not accept ETH as some kind of argument?
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 does accept ETH
as tokenAddress
but @willpote mentioned passing WETH will not change the outcome
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.
true, we do have currencyId
function though and may want to be accurate if it doesn't cost us anything
Feature branch for routing integration.
Loading animation + invalidate stale data visually