initial cut of CLI generation #349
Conversation
| } | ||
| }); | ||
|
|
||
| // TODO parameter for body as input json (--body-input?) |
There was a problem hiding this comment.
Do we anticipate customers requiring JSON input in the first iteration of the CLI? If not maybe we can punt this for later if it's needed?
There was a problem hiding this comment.
I suspect we need it in the first iteration of the CLI at least as much as the customer would.
There was a problem hiding this comment.
it'd be necessary for the $ oxide api command, not so much for the others imo
| }); | ||
|
|
||
| // TODO parameter for body as input json (--body-input?) | ||
| // TODO parameter to output a body template (--body-template?) |
There was a problem hiding this comment.
By body template do you mean a table?
There was a problem hiding this comment.
I'd like to have a parameter that outputs "blank" JSON output so that the user can output that to a file, edit it to fill in appropriate values, and then input it to another option that accepts a JSON-formatted file as input.
| ) -> Result<String> { | ||
| let output = self.cli(spec, crate_name)?; | ||
|
|
||
| let content = rustfmt_wrapper::rustfmt_config( |
There was a problem hiding this comment.
according to #362 , wouldnt rustfmt not be used in the -impl ?
There was a problem hiding this comment.
Good point; we'll work this out.
This is a prototype feature, not ready to be released, but I'd rather have it in the repo than maintaining it in a branch. It shouldn't impact consumers that don't explicitly use it.
Closes oxidecomputer/oxide.rs#46
cc: @david-crespo, @zephraph, @karencfv