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
We still don't have any support for sending a directCommand to the node. This could be very useful for testing many features.
The idea is to have a new command on the CLI (the directCommand), where we just specify the input from a JSON file
Some commands might require additional work, like for instance the ones needing a signature.. or the ones requiring a nonce (we need to get the correct one first)
The text was updated successfully, but these errors were encountered:
This could be very useful for testing many features.
I'm curious about what features would use this? For testing the direct command, we can just use postman...
Not sure what you mean by "features".. Its for testing purposes
I know we can use postman, for the direct commands, but we have to recreate/ copy paste the json all the time we want to test a specific command... If we had some command JSON samples on the cli (like we have for the DDOs on the metadata folder) we could simply run a specific command... and it would just pick the corresponding JSON payload (that we could fine tune if/when needed).
but If nobody else sees value on this, we can close it.. no worries
We still don't have any support for sending a
directCommand
to the node. This could be very useful for testing many features.The idea is to have a new command on the CLI (the directCommand), where we just specify the input from a JSON file
Some commands might require additional work, like for instance the ones needing a signature.. or the ones requiring a nonce (we need to get the correct one first)
The text was updated successfully, but these errors were encountered: