oasisprotocol / oasisprotocol/oasis-core
Move user-facing tooling into its own binary
Open
@Yawning is already working on this.
Since May 9, 2022.
c:cli
epic
s:needs adr
- Dominant language
- Go
- Stars
- 369
- Forks
- 151
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
Over time oasis-node has become a dumping ground for all kinds of subcommands related to end-user functionality. It would be better to split this into two:
- Things related to node control and operation would stay as subcommands in
oasis-node(e.g., requesting node termination, checking its status, etc.). - More user-facing functionality (e.g., generating, signing and transmitting various transactions) would be moved to its own binary, e.g.
oasis-cli.
The part that would move into its own binary would need some usability improvements, e.g. at least support for signer configuration so one wouldn't need to specify all the signer flags on each invocation.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.