-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Command line revamp #4225
Comments
I'd love to have yarn search be a real command but it was a bit tricky when I tried to do as-you-type autocomplete in terminal. Is this something we see as possible with? |
I think Yargs supports automatic completion of bash options. Concierge doesn't yet, but it could be easily adapted. |
I meant a full autocomplete like on the yarn website, but then in terminal |
Oh - that's something that would require an actual UI, right? I think that would be easily doable with mylittledom, but it might be too heavy to be a default command. Here's an example. |
Commander supports nested subcommands from v5. |
Fwiw we have since then started to use Clipanion. |
The current codebase uses Commander. Problem is that we have a lot of custom hacks to support constructs not supported natively by Commander. It degrades the user experience since our hacks don't support all the constructs they should. Some examples:
It would be nice to change our parser to something that would prevent us from having to write such hacks inside Yarn. Some options (I haven't made research on all of them yet):
I'm kinda partial to the last one, in no small part because I wrote it 😄 It would allow us to quickly contribute changes and make releases if we want to support new features, rather than implementing them inside Yarn like we did with commander. It also should support most features we need (promises tolerant, re-entrant, nested subcommands, options forwarding, default help message).
The text was updated successfully, but these errors were encountered: