-
Notifications
You must be signed in to change notification settings - Fork 0
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: asset mgmt base class #75
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
OliverNChalk
requested changes
Sep 7, 2022
OliverNChalk
reviewed
Sep 9, 2022
OliverNChalk
force-pushed
the
feat/asset-mgmt-base-class
branch
from
September 11, 2022 19:19
f415538
to
472c4d0
Compare
OliverNChalk
force-pushed
the
feat/asset-mgmt-base-class
branch
from
September 11, 2022 20:15
472c4d0
to
ffa7c15
Compare
OliverNChalk
approved these changes
Sep 11, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Solution
AssetManagedPairTest::testSetManager
for the table test. If this approach is okay, I will implement it for all tests in the filetestManageReserves_KStillHolds
andtestSync
as the StablePair doesn't have async
function (yet)IAssetManager::adjustManagement()
, is there. reason we are usingint224
in the mock implementation instead ofint256
orint112
?