You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe
The Node.js item is only activated if the current directory contains a package.json file (test -e package.json). The Rust and Go and some other items work similarly (test -e Cargo.toml, test -e go.mod).
If I cd into a subdirectory of the project, the prompt item disappears. For example, I might do cd tests to more easily work on tests.
In my opinion I’m still in the project and would like to see that the project Node.js/Rust/Go/etc version is used.
Describe the solution you'd like
Switch to look-up package.json instead of test -e package.json and so on, where look-up is a function that checks the current directory, then the parent directory and so on until the file is found or the root is hit.
Potential downside: Performance? But we could try and measure?
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe
The Node.js item is only activated if the current directory contains a
package.json
file (test -e package.json
). The Rust and Go and some other items work similarly (test -e Cargo.toml
,test -e go.mod
).If I
cd
into a subdirectory of the project, the prompt item disappears. For example, I might docd tests
to more easily work on tests.In my opinion I’m still in the project and would like to see that the project Node.js/Rust/Go/etc version is used.
Describe the solution you'd like
Switch to
look-up package.json
instead oftest -e package.json
and so on, wherelook-up
is a function that checks the current directory, then the parent directory and so on until the file is found or the root is hit.Potential downside: Performance? But we could try and measure?
The text was updated successfully, but these errors were encountered: