Replies: 3 comments
-
👍 on this, it's also aligned with what @shykes suggested earlier. We could also auto-detect the value (string, json, directory) to omit the flag or raise a warning if the flag is passed. |
Beta Was this translation helpful? Give feedback.
-
I agree that the current UI for inputs needs improvement. A few questions and comments:
OK with me.
Makes perfect sense.
I don’t hate it, but it doesn’t solve the “lots to type” problem. All commands are the same length or longer, except for the special case
In this example, is
Do we still want to implement an interactive command-line wizard? If so, “edit” and “interactive” would be two different modes, right?
I don’t find that intuitive. I would actually expect
That’s a whole other can of worms… IMO better if we discuss that one separately. |
Beta Was this translation helpful? Give feedback.
-
I find the
dagger input
commands a bit cumbersome, there's a lot to type and somehow I always type the wrong thing.What are your thoughts about using flags rather than sub-commands to set the different input types? The obvious downside is "flag mess", but I don't know if that's worse than what we have now.
Examples:
Regular text input (default)
git
dir
secret
list inputs (e.g.
dagger input list
):interactive mode (e.g.
dagger input edit
):Other things:
dagger input unset
would just becomedagger unset
dagger query
could perhaps becomedagger get
? Or, for symmetrical reasons,dagger get
could retrieve inputs (e.g.dagger set foo bar && dagger get foo
)Beta Was this translation helpful? Give feedback.
All reactions