You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Inorder to use ts-relayer as a standalone relayer like hermes, it might make sense to have additional flag of --output <json | yaml | default> for all the queries with ibc-setup *.
Why
To be able to use jq with ibc-setup directly in bash instead of having to create a custom wrapper around the relayer. This will reduce the overhead of running the relayer with the current opperators as well (moving ts-relayer to more production usecases).
Will be a nice to have
The text was updated successfully, but these errors were encountered:
Anmol1696
changed the title
feature: Ability to output in json for ibc-setup
feature: Ability to output in json from ibc-setupOct 13, 2022
Hmmm... looks like there is no abstraction here, just some console.log stuff. Happy if you make all those lines in inc-setup if statements for two outputs. No need to auto-generate them from some meta-format.
Also, note the verbose/debug logs will always be the same. You can just turn down log level for scripts (via -q), so you only get the final (JSON) output.
Overview
Inorder to use ts-relayer as a standalone relayer like hermes, it might make sense to have additional flag of
--output <json | yaml | default>
for all the queries withibc-setup *
.Why
To be able to use
jq
withibc-setup
directly in bash instead of having to create a custom wrapper around the relayer. This will reduce the overhead of running the relayer with the current opperators as well (moving ts-relayer to more production usecases).Will be a nice to have
The text was updated successfully, but these errors were encountered: