From 950e4172719cde107e9dfc2c8c38d88ee0d000ca Mon Sep 17 00:00:00 2001 From: Trevor Brown Date: Mon, 13 Jun 2022 13:24:55 -0400 Subject: [PATCH] docs: remove text from plugin create doc that says utils.bash functions are available (#1247) While the sentence is correct we do not want users relying on `utils.bash` internal functions Related to the conversation on #682 --- docs/plugins/create.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/plugins/create.md b/docs/plugins/create.md index bd07b718..66a43a7d 100644 --- a/docs/plugins/create.md +++ b/docs/plugins/create.md @@ -197,9 +197,8 @@ $ asdf foo bat baz # same as running `$ASDF_DATA_DIR/plugins/foo/lib/commands/co Plugin authors can use this feature to provide utilities related to their tools, or even create plugins that are just new command extensions for asdf itself. -When invoked, if extension commands do not have their executable-bit set, they will be -sourced as bash scripts, having all of the functions from `$ASDF_DIR/lib/utils.bash` available. -Also, the `$ASDF_CMD_FILE` resolves to the full path of the file being sourced. +When invoked, if extension commands do not have their executable-bit set they will be +sourced as bash scripts. Also, the `$ASDF_CMD_FILE` resolves to the full path of the file being sourced. If the executable bit is set, they are just executed and replace the asdf execution. A good example of this feature is for plugins like [`haxe`](https://github.com/asdf-community/asdf-haxe)