-
Notifications
You must be signed in to change notification settings - Fork 2
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
Minimum reserves check #19
Conversation
This reverts commit 5280a86.
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.
Let's add some tests around this. Ideally we'd test that no matter the decimals of the pool tokens the minimum reserves constraint makes sense.
I added some tests. Ideally, these tests will be refactored appropriately in #17. |
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.
As discussed on Slack – let's add tests for removing liquidity.
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 left comments under commit (f24facb#comments) – do you think you can take a look there? ;)
LGTM otherwise 💪
Alternative would be to write a proptest with proper generators but given the amount of tests now that's probably unnecessary.
Potential problemI see that This doesn't look nice to me, considering tokens whose $ value is very high. Take for example that we or someone else wants to create a pair which contains
ETH is a less dramatic example as it costs ~ Questions
|
No description provided.