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

Handling for different versions of CLI tools #2317

Closed
aftix opened this issue Mar 30, 2024 · 1 comment
Closed

Handling for different versions of CLI tools #2317

aftix opened this issue Mar 30, 2024 · 1 comment

Comments

@aftix
Copy link
Contributor

aftix commented Mar 30, 2024

As far as I can tell, the completers are either made for the most recent version of the tool, or carapace calls into completions provided by the command itself. Is there any plans to extend carapace completers to support different versions of tools?

@rsteube
Copy link
Member

rsteube commented Mar 30, 2024

For the most part, no.
It would increase the complexity in regards of maintenance too much.
Users are expected to be able to update their system to recent versions.

Most commands don't change so often so apart from slight version shifts this normally doesn't pose too much of an issue.
In the long term completions are better maintained alongside commands to avoid this.

Current alternatives:

  • Overlay as temporary workaround for missing completions
  • Spec to replace the internal completer with a custom one
  • Bridges to replace the internal completer with a native one

The completers can be built separately. So if the need arises one could also be adapted and maintained externally for a specific version.
Registering these system-wide (e.g. package install) will be possible with System Spec.

@aftix aftix closed this as not planned Won't fix, can't repro, duplicate, stale Mar 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants