Open Avivbens opened 7 months ago
Thanks for this feature request!
To anyone else interested in this feature, please add aย ๐ to the original post at the top to signal that you want this feature, and subscribe if you'd like to be notified.
Thanks for this feature request!
To anyone else interested in this feature, please add aย ๐ to the original post at the top to signal that you want this feature, and subscribe if you'd like to be notified.
Thanks ๐
I think we might need to change the header to โBetter completion for common tools, with contextโ - as Nx is just a subset. Think that this is a game-changer.
Came across this while googling if I can adapt this, after migrating from iterm/fig to warp. This feature would definitely be a reason to stick around for me as I rely heavily on it, and is one of the big things missing for me via ohmyzsh/fig/iterm
Nx
Discord username (optional)
No response
Describe the solution you'd like?
Hi team ๐
I think having a better completion with context might help us a lot. When running
nx run...
- I'd like to have all my available projects, with available targets. Same fornpm
and more tools.A possible solution might be a similar approach to what Fig has - a registry, or some third-party extensions, that will allow CLI creators (me also) to provide you some logic that predict what should be auto-completed right now. It would integrated into your CLI and create a huge impact ๐ฏ
For now, just better completion with context would be awesome, but just throw an idea for some super feature ๐
An example of the change
nx run <ALL_APPS>:<APPS_TARGET>
- with completion.npm i <COMPLETION_FOR_PACKAGES>@<COMPLETION_FOR_VERSIONS>
Is your feature request related to a problem? Please describe.
No response
Additional context
No response
How important is this feature to you?
2
Warp Internal (ignore) - linear-label:39cc6478-1249-4ee7-950b-c428edfeecd1
None