-
Notifications
You must be signed in to change notification settings - Fork 769
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
bash/zsh completions #53
Comments
yargs.completion stuff from what I can tell it seems the filename completion not working is fundamental issue with their script they generate for zsh (I use zsh) I was able to get completion to work for the main commands and then the filesystem to autocomplete after the command completions, however, it overrides the flags I created a ticket on yargs, hopefully get some insight or a potential workaround with the |
I don't think this is something we can work on now, it'll take a ton of work to get this to work well for us since yargs doesn't even list files etc. Should probably unassign and move this to backlog. |
I agree. Moving to the backlog... |
In case this gets picked up, could we have |
We won't be able to do anything about this until yargs/yargs#2113 is resolved but there's been no movement there. Closing for now. |
I don't think closing an issue because it's blocked upstream makes a lot of sense... This is still something that would be good to have, and people want to see, and closing the issue is only going to cause confusion when someone searches for it later and sees it closed as "completed", or this can be addressed down the line. What's the harm in leaving it open and just adding a |
Completions would certainly be nice to have as a feature. The mentioned upstream blocking issue is implemented by yargs/yargs#2331, just hasn't been merged since May. |
Any update on this? |
Blocked by upstream as mentioned |
Any news on this front ? |
@alyssadev We could do a |
I'm not involved in any way, I just wanted to help by indicating that there's an upstream issue that seems to be blocking. |
Oh I see sorry. I might make a PR with the patch! |
The upstream blocking issue is closed as old. Isn't it possible to have shell completions at least for bash without the zsh blocking issue? |
We can leverage
yargs.completion()
to autogenerate bash/zsh completions for wrangler. I tried it, and it's... fine. Annoyingly, it hijacks any suggestions for filenames, and I assume we'll have to reimplement that. Leaving this open if anyone wants a crack at it.The text was updated successfully, but these errors were encountered: