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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Autocompletion when using ENV variables. #146
Comments
Thanks for creating the issue! I think this is pretty doable. |
Yes, this is really annoying especially when dealing with commands that make heavy use of ENV vars. |
I found this issue on https://ovio.org/projects and would love to contribute. Any thoughts or pointers @mschrage ? |
@ericboucher It is part of the internal autocomplete engine, which is not open source. |
Oh, sad... Any idea when this might get addressed? |
Unblocked now! Generators have access to env vars |
Misread, different issue. But this is also done because @fedeci is awesome |
Completion Spec
Fig itself? I don't really know, sorry! 馃檲
Description
When using ENV variables before any command, the autocomplete stops working.
Steps to reproduce
ENV=1
or any combination of{name}={value}
;Expected result
We should see the autocomplete window for what I'm typing.
Actual result
The text was updated successfully, but these errors were encountered: