Adopting tab

[AmirSa12]

We’d love to help you adopt tab in your project! 🚀

If you maintain a CLI in the JavaScript ecosystem and want to provide your users with autocompletion, just drop some details about your tool/repo here, such as:

• The CLI name
• commands/subcommands
• Any flags or options worth highlighting
• recommended values to complete for options that take values

Our team will jump in to create the integration and send over a PR to get you set up.
Just leave the info, and we’ll handle the rest!

[cspotcode]

First off, I hope tab gains traction, because this is exactly what the ecosystem needs: no more reinventing the same completion logic across dozens of different libraries!

What follows is a general question about a style of integration, rather than a request for a specific integration:

Supposing a CLI parser library already implements the logic to generate completions given an argv array. However, this library only supports the bash shell. The authors have written the block of eval'd bash that parses COMP_WORDS, invokes compgen, sets COMPREPLY. But they have not written an equivalent block of code to call pwsh's Register-ArgumentCompleter.

Essentially, of the two responsibilities:
a) generate list of completions based on incomplete input
b) shell-specific interop

...this library has implemented a) but is less interested in implementing b) across every shell known to man: bash, fish, zsh, pwsh, nushell, etc.

Can such a library delegate (b) to @bomb.sh/tab, while using its own implementation of (a)?

The readme's "Quick Start" shows @bomb.sh/tab handling both responsibilities, being informed of the CLI's structure with calls to t.command() and t.option(). Is there an alternative to this?