You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Say we want to save docker build -f ./docker/Dockerfile
This we would save just as HoardCommand{ command: 'docker build -f ./docker/Dockerfile', args: Vec::empty() }
Alternatively, args come into play, if we want to parameterize the saved command
Also I don't think its feasible or even possible to parse all possible commands a user can enter correctly for what their arguments are, and how they are structured now that I think about it.
There are no strict conventions for that
Currently a command is a string. But it should be a union of string and an object. So, we should make this a struct with optional arguments.
Proposal:
So if you run a command with args with no default value, there should spawn an interactive shell.
The text was updated successfully, but these errors were encountered: