Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
More than a pull request, I would like your opinion. I found this tool not entirely matching my workflow. I would rather call this tool from another one and pass JSON rather than so many input files. JSON is not practical for the command line, yet if it comes from another program there is no issue.
I have avoided making big changes to keep code compatibility. In this case I only have a request for the extended public keys at the account level, instead of the payment key level. I want to derive the keys in my tool and not every single time with this tool and generate a new file every time. Consequently when witnessing a transaction, I want to pass from my program a large JSON instead of individually specify each signing key file.
What do you think?