Suggestion support for specific version manager files

[pwall2222]

I have looked around in the docs but I have not found any mentions of this, but it would be a nice to add support for version managers files
Examples:

• .nvmrc docs | code
• .python-version

[aooohan]

vfox has its own version management file, .tool-versions. It is the same as and compatible with asdf.

[aooohan]

vfox will create a .tool-versions file to record SDK version you use when use vfox use -p <sdk-name> command.

[pwall2222]

I did read that on the docs!
I just meant it would be a cool opt-in feature, as per the projects that use those files would remain "less" compatible with vfox

[aooohan]

I did read that on the docs! I just meant it would be a cool opt-in feature, as per the projects that use those files would remain "less" compatible with vfox

Ok, I get what you meant now. To accomplish this, we need to add a new hook for the plugin, which is called when using the vfox use command.

[pwall2222]

That would be brilliant!

[ZuBB]

I did read that on the docs! I just meant it would be a cool opt-in feature, as per the projects that use those files would remain "less" compatible with vfox

Ok, I get what you meant now. To accomplish this, we need to add a new hook for the plugin, which is called when using the vfox use command.

This would be great! Can we expect that .node-version also will be supported?

PS: I just discovered this package, and I am already in love with it!

[aooohan]

I did read that on the docs! I just meant it would be a cool opt-in feature, as per the projects that use those files would remain "less" compatible with vfox

Ok, I get what you meant now. To accomplish this, we need to add a new hook for the plugin, which is called when using the vfox use command.

This would be great! Can we expect that .node-version also will be supported?

If .nvmrc is OK, then .node-version is totally OK! But it's just a work in progress.

PS: I just discovered this package, and I am already in love with it!

Thanks!