-
Notifications
You must be signed in to change notification settings - Fork 13
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(devx): Add filter flag to Iota CLI #2574
Conversation
45d0ed1
to
bf801dd
Compare
ed622b3
to
f5986b6
Compare
f5986b6
to
f1bee6d
Compare
f64c05b
to
bd581a7
Compare
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.
Hey @salaheldinsoliman!
I strongly believe that the functionality you want to expose should be handled exclusively on the client. I made several suggestion that essentially imply that all changes to dependencies (iota-indexer
, iota-json-rpc
, iota-json-rpc-types
) should be reverted.
If you think that you need more options for the queries you are performing to expose this functionality, please create issues with the respective feature request so as to discuss them and plan them accordingly.
cbfe84a
to
ced0ed6
Compare
d28267d
to
79b63ea
Compare
Signed-off-by: salaheldinsoliman <[email protected]>
Signed-off-by: salaheldinsoliman <[email protected]>
Signed-off-by: salaheldinsoliman <[email protected]>
Signed-off-by: salaheldinsoliman <[email protected]>
|
Signed-off-by: salaheldinsoliman <[email protected]>
Signed-off-by: salaheldinsoliman <[email protected]>
Signed-off-by: salaheldinsoliman <[email protected]>
@Thoralf-M @DaughterOfMars Would it make sense to merge this at this stage (before the release)? |
Not with failing tests, I would say |
The failing tests don't seem to be related to this PR, I don't see a reason not to merge it before the release |
Still a lot of comments I would prefer to be resolved first, but I'm not going to fight too hard |
Nothing against that, but to me it looks like all of them are outdated (one from you #2574 (comment)) the others from @kodemartin Only this tiny suggestion is still open, but also not important #2574 (comment) |
Co-authored-by: Thoralf-M <[email protected]>
Signed-off-by: salaheldinsoliman <[email protected]>
* fix(cli): fix cli_tests made by #2574 Signed-off-by: salaheldinsoliman <[email protected]> * fix(cli): use default_value Signed-off-by: salaheldinsoliman <[email protected]> * fix(cli): run cargo fmt Signed-off-by: salaheldinsoliman <[email protected]> * fix(cli): properly parse EmitOptions Signed-off-by: salaheldinsoliman <[email protected]> * fix(cli): fix prerender_clever_errors Signed-off-by: salaheldinsoliman <[email protected]> --------- Signed-off-by: salaheldinsoliman <[email protected]>
Description of change
This PR adds an
emit
flag toiota client call
, whose functionality is to filter the outputs of the command.The flag takes
"effects" | "input" | "events" | "object_changes" | "balance_changes"
as possible args.This addresses the issue that
call
command result is often too long.Note: the PR only addresses
call
. If the approach is agreed upon, it can be extended toptb
as wellLinks to any relevant issues
fixes #2015
Type of change
Choose a type of change, and delete any options that are not relevant.
How the change has been tested
iota/tests/cli_tests
Change checklist
Tick the boxes that are relevant to your changes, and delete any items that are not.