Skip to content
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

[Feature Request] Separate "restrict to version X" and "install version X" functionalities #1765

Open
DerekTBrown opened this issue Jul 3, 2024 · 0 comments

Comments

@DerekTBrown
Copy link

Is your feature request related to a problem? Please describe

User Story

  • As a user, I want to be able to enforce that all sub-folders in a given repository use Python X.X.X, but I don't want to require users to install Python X.X.X when they run asdf install in the root of the repository: I only want installation to happen when users run asdf install in a project sub-folder.
  • This feature is critical for working in multi-langauge repositories: it prevents users from having to download a huge toolchain whenever they are working on a specific project.

Describe the proposed solution

Introduce two features:

  1. noinstall
    Following a version in a .tool-versions file, a user can add noinstall:
golangci-lint 1.59.1 noinstall

This line is functionally skipped when running asdf install

  1. inherit
    In place of a version in a .tool-versions file, a user can specify inherit:
golangci-lint inherit

Since this doesn't have the noinstall flag, the parent version would be installed.

Describe similar asdf features and why they are not sufficient

asdf doesn't have this functionality today.

Describe other workarounds you've considered

  • Creating separate linters that look at .tool-versions file. This is clumsy.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant