-
Notifications
You must be signed in to change notification settings - Fork 161
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
Update examples for new v3-sdk version #61
base: main
Are you sure you want to change the base?
Conversation
Feat/oracle
Advanced Examples
Remove unused functions and constants in range-order, update readme. Return actual target price of range order instead of user defined price from which order is created
Feat/advanced
Add get pool data via multicall code example
Remove unused Wallet, rename multicall provider
Update quoting example
Switch quoting example to quoteExactInput function
Feat/trading updated
…n-update Feat/release sdk version update
Import packages from foundation npm
Update V3 sdk version
Fix/release patch
…der-router Add deprecation notice to routing and swap-and-add-liquidity
👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎ This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored. Ignoring: Next stepsTake a deeper look at the dependencyTake a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev. Remove the packageIf you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency. Mark a package as acceptable riskTo ignore an alert, reply with a comment starting with |
@SocketSecurity ignore npm/@uniswap/[email protected] |
How does this bot not recognize 4.0.0 is newer than 3.3.0 |
@Florian-S-A-W Sorry about this, I'll look into why Socket is not recognizing version 4. Feel free to merge anyway. |
@@ -6,8 +6,8 @@ | |||
"@types/node": "^16.7.13", | |||
"@types/react": "^18.0.0", | |||
"@types/react-dom": "^18.0.0", | |||
"@uniswap/sdk-core": "^3.1.0", | |||
"@uniswap/v3-sdk": "^3.9.0", | |||
"@uniswap/sdk-core": "npm:@uniswapfoundation/sdk-core@^5.0.0", |
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.
Note to self: this appears to be where the issue is
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.
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.
Update: This is not the issue
I know this message doesn't make much sense, but the package Is it possible to bump the package to |
version "3.0.1" | ||
resolved "https://registry.yarnpkg.com/@uniswap/v2-sdk/-/v2-sdk-3.0.1.tgz#690c484104c1debd1db56a236e5497def53d698b" | ||
integrity sha512-eSpm2gjo2CZh9FACH5fq42str/oSNyWcDxB27o5k44bEew4sxb+pld4gGIf/byJndLBvArR9PtH8c0n/goNOTw== | ||
"@uniswap/v2-sdk@npm:@uniswapfoundation/v2-sdk@^4.0.0": |
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.
This is the line that is causing the GitHub bot to get confused. It should be loading @uniswapfoundation/v2-sdk
not @uniswap/v2-sdk
.
Sorry about this mistake.
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.
Thanks @mikolalysenko. This should be the undeprecated package https://www.npmjs.com/package/@uniswapfoundation/v2-sdk
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.
I'll update this package to a newer version.
Fix smart-order-router version in swap-and-add-liquidity example
The latest commit fixes this issue @mr-uniswap |
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.
.github/workflows/lint-v3-sdk-collecting-fees.yaml
There are no changes to the lint that fails here. |
|
||
// Currencies and Tokens | ||
|
||
export const WETH_TOKEN = new Token( | ||
SupportedChainId.MAINNET, | ||
SUPPORTED_CHAINS[0], |
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.
Did you consider importing ChainId
instead? Then you can do ChainId.MAINNET
on line 13 and 21
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.
Yeah that would make more sense here.
Update all examples to use the new v3-sdk version published by the Uniswap foundation.
Delete multicall example.