Your Name
6501674809
feat(golang-rewrite): implement asdf plugin extension commands
...
* Enable `plugin_extension_command.bats` tests
* Add comment on `version_commands.bats` tests
* Show help output when asdf run with no arguments
* Document breaking change in asdf extension commands feature
* Create `Plugin.ExtensionCommandPath` method
* Create `asdf cmd` subcommand
* Get `plugin_extension_command.bats` tests passing
* Document breaking changes to asdf extension commands
2024-12-18 10:22:06 -05:00
Edwin Kofler
90ead5ea0a
chore: Fix ShellCheck errors in tests ( #1459 )
...
Closes https://github.com/asdf-vm/asdf/issues/1396
2023-01-27 23:17:41 +11:00
Edwin Kofler
28b348a041
chore: Fix ShellCheck errors in tests ( #1450 )
2023-01-23 15:29:18 +11:00
Josh Soref
eaf2215cb8
chore: Fix spelling ( #1289 )
...
chore: Fix spelling
2022-07-05 09:40:33 -04:00
James Hegedus
21bc411915
ci: add latest OSs to testing matrix, bump BATS, shfmt, shellcheck ( #1260 )
...
* ci: add latest OSs to testing matrix
* ci: bump bats & shellcheck & shfmt
* chore: format with latest shfmt
2022-06-24 19:20:27 +10:00
Yasunori Fujie
3e0cb9aaea
fix: help for extension commands for plugins with hyphens in the name. ( #1048 )
...
* test: add test for plugin command list in asdf help
* fix: help for plugins containing hyphens
2021-09-23 14:47:26 -04:00
Victor Hugo Borja
a26bed6586
Make sure extension commands are properly displayed by asdf help
2020-03-15 11:45:09 -06:00
Trevor Brown
8b90d883ee
Require .bash extension for plugin extension commands
2020-03-02 13:13:20 -05:00
Victor Hugo Borja
e968fe6142
Subcommand-aware command line interface.
2019-11-27 12:17:17 -06:00
Victor Hugo Borja
70099027c2
Move plugin extension command into it's own file.
...
Add a test for calling default command with arguments.
2019-11-25 12:07:55 -06:00
Victor Hugo Borja
a22733f819
Resolve asdf PLUGIN_NAME default command.
...
When calling `asdf foo` and the `foo` plugin provides a `bin/default-command`
2019-11-25 02:47:55 -06:00
Victor Hugo Borja
0e8e1f8f84
New feature: asdf extension commands
...
It's possible for plugins to define new asdf commands. This way plugins can extend asdf capabilities or expose utilities related to their managed tool.
For example, a `foo` plugin might expose the command `asdf foo bar` by providing an executable file at `bin/bar`.
If `bin/bar` is a file but has no executable bit set, then its considered a source-able bash script, and will be sourced
with all the functions in `$ASDF_DIR/lib/utils.sh` already loaded.
A good example of this feature is the `nodejs` plugin, where people must import the release team keyring before
installing a nodejs version. People can execute the following command without having to know where exactly is the plugin located.
2019-11-25 02:24:46 -06:00
