fix(gnokey): JSON-ify the query results from the 'gnokey' query
From issue of @leohhhn : https://github.com/gnolang/gno/issues/2232
Contributors' checklist...
- [ ] Added new tests, or not needed, or not feasible
- [ ] Provided an example (e.g. screenshot) to aid review or the PR is self-explanatory
- [ ] Updated the official documentation or not needed
- [ ] No breaking changes were made, or a
BREAKING CHANGE: xxxmessage was included in the description - [ ] Added references to related issues and PRs
- [ ] Provided any useful hints for running manual tests
- [ ] Added new benchmarks to generated graphs, if any. More info here.
Codecov Report
Attention: Patch coverage is 20.45455% with 70 lines in your changes missing coverage. Please review.
:loudspeaker: Thoughts on this report? Let us know!
I don't like this. The default output for
vm/qevalshould be simple and human-readable; JSON is helpful for working with scripting but harms readability. Ie. I want the result ofvm/qevalto be simple to understand and close to what I get reading the result ofmaketx call.I suggest having a
-outputflag, defaulting totext, but which can be set tojson, for the gnokeyquery,maketx -broadcastandbroadcastcommands. This should print the JSON response from the node, with little modification. In the case ofqeval, this can be simplyqres.Response.
agree with u, so that i will also format response when calling maketx --broadcast.
We need to align this pull request with #1776 to ensure consistency and idiomatic usage.
I suggest waiting for #1776 to be merged before merging this one.
cc @gfanton
This PR is stale because it has been open 3 months with no activity. Remove stale label or comment or this will be closed in 3 months.
I'm closing this PR as the author has not been contributing to Gno for a while.
Feel free to re-open this PR, or fork this PR and propose a new one, considering the latest comments and any surrounding discussion.