propose new request-update command #616
Conversation
There was a problem hiding this comment.
Looks good, I have a few comments / questions in the review. I think it'd be good to get this merged in soon. I think it'd be good to get like a 'status' on different operations in our design docs, so we can mark that this is 'not yet implemented', but having it in the doc makes the plan clear. Then we can have a workflow where implementors of functionality should update the design-doc status.
| User Story: As a CLI user I would like to create a request for an order from a | ||
| template, overriding the name. | ||
|
|
||
| ``` | ||
| $ planet orders request --like - --name IAmACopy < request.json |
There was a problem hiding this comment.
Why would you use the '<' here instead of just planet orders request --like request.json --name IAmACopy? The '<' is still beyond my command-line knowledge.
There was a problem hiding this comment.
yeah, really, there is no reason for using < requests.json instead of just using requests.json
|
@cholmes FYI |
|
|
||
| $ planet orders request \ |
There was a problem hiding this comment.
from flags to positional
note, this is likely not a pre-release issue and can be treated as low-priority
This update to the CLI-Orders design doc is a proposal for not implementing the
--likefunctionality inplanet orders requestbut instead creating a new command,planet orders request-updatewhich will implement the--likefunctionality. This allowsplanet orders requestto have required options actually be arguments (saves many keystrokes and trial and error).