-
Notifications
You must be signed in to change notification settings - Fork 103
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(ecocredit/marketplace): buy direct cli commands #1008
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1008 +/- ##
==========================================
- Coverage 59.86% 59.76% -0.10%
==========================================
Files 231 231
Lines 22840 22918 +78
==========================================
+ Hits 13674 13698 +24
- Misses 7842 7891 +49
- Partials 1324 1329 +5
Flags with carried forward coverage won't be shown. Click here to find out 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.
Looking good. Do we need to create a followup task for adding the integration tests or can we include those here? I think we can include them here without conflicting with #901 but maybe I'm missing something.
x/ecocredit/client/marketplace/tx.go
Outdated
[ | ||
{ | ||
"sell_order_id": 52, | ||
"quantity": "32.5", | ||
"bid_price": {"denom": "uregen", "amount": "32000000"}, | ||
"disable_auto_retire": false, | ||
"retirement_location": "US-NY" | ||
}, | ||
]`), |
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.
We should probably be consistent with how we do batch orders in the create sell order and update sell order commands. We use yaml there but we use json here.
Any reason you chose json over yaml? Should we update here or there? cc @aleem1314
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 not sure, i know we have that gen-batch-json command, so that's what i had in mind with this PR. I can change my PR here, but i dont think that would be the end of our inconsistencies 🤷🏻
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.
ill look into adding tests as well
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.
so looks like our CLI integration tests are still commented out until our test suite is wired up to work with ORM. i think we had this issue when we did our v3 sprint.
should be able to add tests for this once the wiring mayhem is done
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.
until our test suite is wired up to work with ORM
This should be good to go now that #901 is merged, correct?
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.
not exactly,,
regen-ledger/x/ecocredit/client/testsuite/tx.go
Lines 52 to 61 in 88232d6
// TODO: enable integrations test after ORM migration | |
// suite.Run(t, NewIntegrationTestSuite(cfg)) | |
// // setup another cfg for testing ecocredit enabled class creators list. | |
// genesisState := ecocredit.DefaultGenesisState() | |
// genesisState.Params.AllowlistEnabled = true | |
// bz, err := cfg.Codec.MarshalJSON(genesisState) | |
// require.NoError(t, err) | |
// cfg.GenesisState[ecocredit.ModuleName] = bz | |
// suite.Run(t, NewAllowListEnabledTestSuite(cfg)) |
#901 switched the client impls to use the updated types, but the tests are not updated yet.
waiting for #1026 to add tests and merge |
Moving forward, we will treat cli tests as a last priority and as a nice to have in the backlog. |
Description
Closes: #983
Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...
!
to the type prefix if API or client breaking changeCHANGELOG.md
Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...
!
in the type prefix if API or client breaking change