- Remove environment variables from all --help messages

Author: DannyBen

lib/bashly/commands/add.rb

@@ -53,10 +53,6 @@ class Add < Base
       example 'bashly add comp function'
       example 'bashly add comp script completions.bash'
 
-      environment 'BASHLY_SOURCE_DIR', 'The path containing the bashly configuration and source files [default: src]'
-      environment 'BASHLY_LIB_DIR', 'The path to use for creating the library files, relative to the source dir ' \
-        '[default: lib]'
-
       attr_reader :skip_src_check
 
       def colors_command

lib/bashly/commands/generate.rb

@@ -13,26 +13,11 @@ class Generate < Base
       option '-u --upgrade', 'Upgrade all added library functions'
       option '-w --watch', 'Watch the source directory for changes and regenerate on change'
       option '-r --wrap FUNCTION', 'Wrap the entire script in a function so it can also be sourced'
-      option '-e --env ENV', 'Force the generation environment (see BASHLY_ENV)'
-
-      environment 'BASHLY_SOURCE_DIR', 'The path containing the bashly configuration and source ' \
-        'files [default: src]'
-
-      environment 'BASHLY_TARGET_DIR', 'The path to use for creating the bash script [default: .]'
-      environment 'BASHLY_LIB_DIR',
-        'The path to use for upgrading library files, relative to the source dir [default: lib]'
-
-      environment 'BASHLY_STRICT', 'When not empty, enable bash strict mode (set -euo pipefail)'
-      environment 'BASHLY_TAB_INDENT',
-        'When not empty, the generated script will use tab indentation instead of spaces ' \
-          '(every 2 leading spaces will be converted to a tab character)'
-
-      environment 'BASHLY_ENV', <<~HELP
-        Set to 'production' or 'development':
+      option '-e --env ENV', <<~HELP
+        Force the generation environment:
+        
         - production    generate a smaller script, without file markers
         - development   generate with file markers
-
-        Can be overridden with --env [default: development]
       HELP
 
       example 'bashly generate --force'

lib/bashly/commands/init.rb

@@ -9,8 +9,6 @@ class Init < Base
 
       option '-m --minimal', 'Use a minimal configuration file (without commands)'
 
-      environment 'BASHLY_SOURCE_DIR', 'The path to use for creating the configuration file [default: src]'
-
       def run
         if Dir.exist?(target_dir) && !Dir.empty?(target_dir)
           raise InitError, "Directory g`#{target_dir}` already exists and is not empty"

lib/bashly/commands/preview.rb

@@ -6,8 +6,6 @@ class Preview < Base
       usage 'bashly preview'
       usage 'bashly preview (-h|--help)'
 
-      environment 'BASHLY_SOURCE_DIR', 'The path containing the bashly configuration and source files [default: src]'
-
       def run
         with_valid_config do
           command = Script::Command.new config

lib/bashly/commands/validate.rb

@@ -11,8 +11,6 @@ class Validate < Base
       option '-v --verbose', 'Show the bashly configuration file prior to validating. ' \
         'This is useful when using split config (import) since it will show the final compiled configuration.'
 
-      environment 'BASHLY_SOURCE_DIR', 'The path containing the bashly configuration and source files [default: src]'
-
       def run
         if args['--verbose']
           lp config

spec/approvals/cli/add/help

@@ -70,14 +70,6 @@ Parameters:
     For the 'comp script' or 'comp yaml' commands: path to output file.
     In all cases, this is optional and will have sensible defaults.
 
-Environment Variables:
-  BASHLY_SOURCE_DIR
-    The path containing the bashly configuration and source files [default: src]
-
-  BASHLY_LIB_DIR
-    The path to use for creating the library files, relative to the source dir
-    [default: lib]
-
 Examples:
   bashly add strings --force
   bashly add comp function

spec/approvals/cli/generate/help

@@ -21,36 +21,14 @@ Options:
     Wrap the entire script in a function so it can also be sourced
 
   -e --env ENV
-    Force the generation environment (see BASHLY_ENV)
+    Force the generation environment:
+    
+    - production    generate a smaller script, without file markers
+    - development   generate with file markers
 
   -h --help
     Show this help
 
-Environment Variables:
-  BASHLY_SOURCE_DIR
-    The path containing the bashly configuration and source files [default: src]
-
-  BASHLY_TARGET_DIR
-    The path to use for creating the bash script [default: .]
-
-  BASHLY_LIB_DIR
-    The path to use for upgrading library files, relative to the source dir
-    [default: lib]
-
-  BASHLY_STRICT
-    When not empty, enable bash strict mode (set -euo pipefail)
-
-  BASHLY_TAB_INDENT
-    When not empty, the generated script will use tab indentation instead of
-    spaces (every 2 leading spaces will be converted to a tab character)
-
-  BASHLY_ENV
-    Set to 'production' or 'development':
-    - production    generate a smaller script, without file markers
-    - development   generate with file markers
-    
-    Can be overridden with --env [default: development]
-
 Examples:
   bashly generate --force
   bashly generate --wrap my_function

spec/approvals/cli/init/help

@@ -13,7 +13,3 @@ Options:
 
   -h --help
     Show this help
-
-Environment Variables:
-  BASHLY_SOURCE_DIR
-    The path to use for creating the configuration file [default: src]

spec/approvals/cli/preview/help

@@ -7,7 +7,3 @@ Usage:
 Options:
   -h --help
     Show this help
-
-Environment Variables:
-  BASHLY_SOURCE_DIR
-    The path containing the bashly configuration and source files [default: src]

spec/approvals/cli/validate/help

@@ -12,7 +12,3 @@ Options:
 
   -h --help
     Show this help
-
-Environment Variables:
-  BASHLY_SOURCE_DIR
-    The path containing the bashly configuration and source files [default: src]