oasisprotocol / oasisprotocol/oasis-core
Add ability to handle additional command-line arguments to the `contract_client!` macro
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 369
- Forks
- 151
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
The contract_client! macro from the client_utils crate should have a way to handle additional applicatiton arguments on the command-line.
Details
The contract_client! macro creates a clap::App instance, parses all the arguments and creates the enclave API client all at once. Sometimes it would be useful to be able to give an additional argument to a client on the command-line (e.g. in clients/test-db-encryption/src/main.rs, the key manager's mrenclave could be provided on the command-line as is done elsewhere).
Acceptance Criteria
- The
client_utilscrate provides a way to specify additional command-line arguments when using thecontract_client!macro.
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.
Research direction
Start in the client_utils crate and inspect the contract_client! macro, then compare its argument parsing with clients/test-db-encryption/src/main.rs and the other command-line usage mentioned in the issue. Define how callers can provide extra arguments while preserving the existing enclave API client setup, and verify the acceptance criterion with the relevant client or macro tests if present.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, developer-experience
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100