bashly 0.6.0 → 0.6.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 7fe733a46c8634cc39b4c792b177ca9ac7610a8d408714fa482b3c0ad15fc10f
-  data.tar.gz: 908960de1cb2d682ff801630e0f6667a42df171612ed6a92aee72bcc369cc0e2
+  metadata.gz: 650f456561f180e0a39b2e6e0c66f6c5913438ac6301d44bff064470d602daba
+  data.tar.gz: 2f64d00edb50ce738d506568600d8b73b898aad6563990460a80a52d912a6e66
 SHA512:
-  metadata.gz: 9e0dcf39faf63d5d798fac7ed41768994ec6715a58b898e390ec2a6019948497d314c08bc8ce1041fb5f1a105884a04d759e258085fdcf7fbbe87af1c4a7a4e0
-  data.tar.gz: 83279b0a7df6eb6f3c2a779bbc54221e9cad58e6e08c4a207f1d592aa12329cc488d7169b682191be02474f098dbfda0f3d6ad6cd03e3a91e1bf793bb29fcdc3
+  metadata.gz: 70427709c22c05bcfdfadb1daafaea8c87c5854b03488913c916ffb29861521c853eb5392f22c0c79b7bdc8fe359fc55389c0d6f0540493c250dd6ba1f7d79b5
+  data.tar.gz: 2b2aa5dc0525edc81ce3c023583b0d829907de9e1656a00fdb37d6cd87e0b4ab788e70e71fe51763a661006f8ce8fdf950a7c3e7ffcce095edec5cc799e942ed

data/README.md

@@ -3,405 +3,67 @@
 
 # Bashly - Bash CLI Framework and Generator
 
-Create beautiful bash scripts from simple YAML configuration
+Create feature-rich bash scripts using simple YAML configuration
 
 [![Gem Version](https://badge.fury.io/rb/bashly.svg)](https://badge.fury.io/rb/bashly)
 [![Build Status](https://github.com/DannyBen/bashly/workflows/Test/badge.svg)](https://github.com/DannyBen/bashly/actions?query=workflow%3ATest)
 [![Maintainability](https://api.codeclimate.com/v1/badges/8cf89047e50ca601e431/maintainability)](https://codeclimate.com/github/DannyBen/bashly/maintainability)
 
+## [bashly.dannyb.co](https://bashly.dannyb.co)
+
 ---
 
 ![demo](demo/cast.svg)
 
 </div>
 
+Bashly is a command line application (written in Ruby) that lets you
+generate feature-rich bash command line tools.
 
-## Table of Contents
-
-- [Table of Contents](#table-of-contents)
-- [Installation](#installation)
-- [Prerequisites](#prerequisites)
-- [What is Bashly](#what-is-bashly)
-- [Usage](#usage)
-  - [Using the input arguments in your code](#using-the-input-arguments-in-your-code)
-- [Examples](#examples)
-- [Configuration Reference](#configuration-reference)
-  - [Command options](#command-options)
-  - [Argument options](#argument-options)
-  - [Flag options](#flag-options)
-  - [Environment Variable options](#environment-variable-options)
-- [Extensible Scripts](#extensible-scripts)
-- [Bash Completions](#bash-completions)
-- [Real World Examples](#real-world-examples)
-- [Contributing / Support](#contributing--support)
-
----
-
-
-## Installation
-
-```shell
-$ gem install bashly
-```
+Bashly lets you focus on your specific code, without worrying about command line
+argument parsing, usage texts, error messages and other functions that are
+usually handled by a framework in any other programming language.
 
-or with Docker:
+It is available both as a [ruby gem](https://rubygems.org/gems/bashly) and as
+a [docker image](https://hub.docker.com/r/dannyben/bashly).
 
-```shell
-$ alias bashly='docker run --rm -it --volume "$PWD:/app" dannyben/bashly'
-```
 
-## Prerequisites
+## Documentation
 
-The bash scripts generated by bashly require bash 4 or higher due to heavy
-use of associative arrays.
+- [Bashly Homepage][docs]
+- [Examples][examples]
 
+## How it works
 
-## What is Bashly
+1. You provide a YAML configuration file, describing commands, sub-commands,
+   arguments, and flags. Running `bashly init` creates an initial sample YAML
+   file for you ([example](https://github.com/DannyBen/bashly/tree/master/examples/minimal#bashlyyml)).
+2. Bashly then automatically generates a bash script (when you run
+   `bashly generate`) that can parse and validate user input, provide help
+   messages, and run your code for each command ([example](https://github.com/DannyBen/bashly/blob/master/examples/minimal/download)).
+3. Your code for each command is kept in a separate file, and can be merged
+   again if you change it ([example](https://github.com/DannyBen/bashly/blob/master/examples/minimal/src/root_command.sh)).
 
-Bashly is a command line application (written in Ruby) that lets you generate
-feature-rich bash command line tools.
+## Features
 
-The design intention is to let you focus on your specific code, without 
-worrying about command line argument parsing, usage texts, error messages
-and other functions that are usually handled by a framework in any other
-programming language.
-
-Bahsly is responsible for:
+Bashly is responsible for:
 
 - Generating a **single, standalone bash script**.
-- Generating **usage texts** and help screens, showing your tool's arguments, 
-  flags and commands (works for subcommands also).
+- Generating **usage texts** and help screens, showing your tool's arguments, flags and commands (works for sub-commands also).
 - Parsing the user's command line and extracting:
   - Optional or required **positional arguments**.
   - Optional or required **option flags** (with or without flag arguments).
-  - **Commands** (and subcommands).
+  - **Commands** (and sub-commands).
   - Standard flags (like **--help** and **--version**).
 - Preventing your script from running unless the command line is valid.
-- Providing you with a place to input your code for each of the functions 
-  your tool performs, and merging it back to the final script.
-- Providing you with additional (optional) framework-style, standard
-  library functions:
+- Providing you with a place to input your code for each of the functions your tool performs, and merging it back to the final script.
+- Providing you with additional (optional) framework-style, standard library functions:
   - **Color output**.
   - **Config file management** (INI format).
   - **YAML parsing**.
   - **Bash completions**.
   - and more.
 
-
-## Usage
-
-The `bashly.yml` file can be set up to generate two types of scripts:
-
-1. Script with commands (for example, like `docker` or `git`).
-2. Script without commands (for example, like `ls`)
-
-This is detected automatically by the contents of the configuration: If it
-contains a `commands` definition, it will generate a script with commands.
-
-In an empty directory, create a sample configuration file by running
-
-```shell
-$ bashly init
-# or, to generate a simpler configuration:
-$ bashly init --minimal
-```
-
-This will create a sample `src/bashly.yml` file.
-You can edit this file to specify which arguments, flags and commands you
-need in your bash script.
-
-Then, generate an initial bash script and function placeholder scripts by
-running
-
-```shell
-$ bashly generate
-```
-
-This will:
-
-1. Create the bash executable script.
-2. Create files for you to edit in the `src` folder.
-
-Finally, edit the files in the `src` folder. Each of your script's commands
-get their own file. Once you edit, run `bashly generate` again to merge the
-content from your functions back into the script.
-
-### Using the input arguments in your code
-
-In order to access the parsed arguments in any of your partial scripts, you
-may simply access the `$args` associative array.
-
-For example:
-
-1. Generate a minimal configuration with `bashly init --minimal`
-2. Generate the bash script with `bashly generate`
-3. Run the script with `./download hello --force`
-
-You will notice that all the arguments of the associative array are printed 
-on screen. This is done by the `inspect_args` function that was inserted into
-the generated partial script `src/root_command.sh`.
-
-You can now access these variables by modifying `sec/root_command.sh` like
-this:
-
-
-```bash
-# src/root_command.sh
-source_url=${args[source]}
-force=${args[--force]}
-
-if [[ $force ]]; then
-  echo "downloading $source_url with --force"
-else
-  echo "downloading $source_url"
-fi
-```
-
-After editing the file, run `bashly generate` (or `bashly g` for short) and
-run:
-
-```
-$ ./download a --force
-downloading a with --force
-```
-
-
-## Examples
-
-The [examples folder](examples#readme) contains many detailed and documented 
-example configuration files, with their output.
-
-
-## Configuration Reference
-
-The `bashly.yml` configuration file consists of these types:
-
-- [Command](#command-options) - defines the root command as well as any 
-  subcommand.
-- [Argument](#argument-options) - defines positional arguments.
-- [Flag](#flag-options) - defines option flags.
-- [Environment Variable](#environment-variable-options) - defines 
-  environment variables required (or desired) by your script.
-
-### Command options
-
-Unless otherwise specified, these definitions can be used for both the root
-command and subcommands (under the `commands` definition).
-
- Option    | Description
------------|-------------
-`name`     | The name of the script or subcommand.
-`short`    | An additional, optional pattern - usually used to denote a one letter variation of the command name. You can add `*` as a suffix, to denote a "starts with" pattern - for example `short: m*`. *Applicable only in subcommands*.
-`help`     | The header text to display when using `--help`. This option can have multiple lines. In this case, the first line will be used as summary wherever appropriate.
-`version`  | The string to display when using `--version`. *Applicable only in the main command*.
-`default`  | Setting this to `true` on any command, will cause any unrecognized command line to be passed to this command. *Applicable only in subcommands*.
-`extensible` | Specify that this command can be [externally extended](#extensible-scripts). *Applicable only in the main command*.
-`examples` | Specify an array of examples to show when using `--help`. Each example can have multiple lines.
-`environment_variables` | Specify an array of [environment variables](#environment-variable-options) needed by your script. 
-`commands` | Specify the array of [commands](#command-options). Each command will have its own args and flags. Note: if `commands` is provided, you cannot specify flags or args at the same level.
-`args`     | Specify the array of [positional arguments](#argument-options) this script needs.
-`flags`    | Specify the array of option [flags](#flag-options) this script needs.
-`completions` | Specify an array of additional completion suggestions when used in conjunction with `bashly add comp`. See [Bash Completions](#bash-completions).
-`catch_all` | Specify that this command should allow for additional arbitrary arguments or flags. It can be set in one of three ways:<br>- Set to `true` to just enable it.<br>- Set to a string, to use this string in the usage help text.<br>- Set to a hash containing `label` and `help` keys, to show a detailed help for it when running with `--help`.
-`dependencies` | Specify an array of any required external dependencies (commands). The script execution will be halted with a friendly error unless all dependency commands exist.
-`group`    | In case you have many commands, use this option to specify a caption to display before this command. This option is purely for display purposes, and needs to be specified only for the first command in each group.
-`footer` | Add a custom message that will be displayed at the end of the `--help` text. 
-
-### Argument options
-
-The argument's value will be available to you as `${args[user]}` in your 
-bash function.
-
- Option    | Description
------------|-------------
-`name`     | The name of the argument.
-`help`     | The message to display when using `--help`. Can have multiple lines.
-`required` | Specify if this argument is required. Note that once you define an optional argument (without required: true) then you cannot define required arguments after it.
-`default`  | The value to use in case it is not provided by the user. Implies that this argument is optional.
-`allowed`  | Limit the allowed values by providing an array.
-
-### Flag options
-
-The flag's value will be available to you as `${args[--output]}` in your 
-bash function (regardless of whether the user provided it with the long or 
-short form).
-
- Option    | Description
------------|-------------
-`long`     | The long form of the flag.
-`short`    | The short form of the flag.
-`help`     | The text to display when using `--help`. Can have multiple lines.
-`arg`      | If the flag requires an argument, specify its name here.
-`required` | Specify if this flag is required.
-`default`  | The value to use in case it is not provided by the user. Implies that this flag is optional, and only makes sense when the flag has an argument.
-`allowed`  | For flags with an argument, you can limit the allowed values by providing an array.
-
-#### Special handling for -v and -h
-
-The `-v` and `-h` flags will be used as the short options for `--version` and
-`--help` respectively **only if you are not using them in any of your own
-flags**.
-
-### Environment variable options
-
-If an environment variable is defined as required (false by default), the
-execution of the script will be halted with a friendly error if it is not
-set.
-
- Option    | Description
------------|-------------
-`name`     | The name of the variable (it will be automatically capitalized).
-`help`     | The message to display when using --help. Can have multiple lines.
-`required` | Specify if this variable is required.
-
-
-## Extensible Scripts
-
-You may configure your generated bash script to delegate any unknown command
-to an external executable, by setting the `extensible` option to either `true`,
-or to a different external command.
-
-This is similar to how `git` works. When you execute `git whatever`, the `git`
-command will look for a file named `git-whatever` in the path, and execute it.
-
-Note that this option cannot be specified together with the `default` option,
-since both specify a handler for unknown commands.
-
-The `extensible` option supports two operation modes:
-
-### Extension Mode (`extensible: true`)
-
-By setting `extensible` to `true`, a specially named executable will be called
-when an unknown command is called by the user.
-
-Given this `bashly.yml` configuration:
-
-```yaml
-name: myscript
-help: Example
-version: 0.1.0
-extensible: true
-
-commands:
-- name: upload
-  help: Upload a file
-```
-
-And this user command:
-
-```
-$ myscript something
-
-```
-
-The generated script will look for an executable named `myscript-something` 
-in the path. If found, it will be called.
-
-See the [extensible example](examples/extensible).
-
-
-### Delegate Mode (`extensible: <executable name>`)
-
-By setting `extensible` to any string, unknown command calls by the user will
-be delegated to the executable with that name.
-
-Given this `bashly.yml` configuration:
-
-```yaml
-name: mygit
-help: Example
-version: 0.1.0
-extensible: git
-
-commands:
-- name: push
-  help: Push to my repository
-```
-
-And this user command:
-
-```
-$ mygit status
-
-```
-
-The generated script will execute `git status`.
-
-See the [extensible-delegate example](examples/extensible-delegate).
-
-
-## Bash Completions
-
-Bashly comes with built-in bash completions generator, provided by the 
-[completely][completely] gem.
-
-By running any of the `bashly add comp` commands, you can add this
-functionality to your script in one of three ways:
-
-- `bashly add comp function` - creates a function in your `./src/lib` directory
-   that echoes a completion script. You can then call this function from any
-   command (for example `yourcli completions`) and your users will be able to 
-   install the completions by running `eval "$(yourcli completions)"`.
-- `bashly add comp script` - creates a standalone completion script that can be
-  sourced or copies to the system's bash completions directory.
-- `bashly add comp yaml` - creates the "raw data" YAML file. This is intended
-  mainly for development purposes.
-
-The bash completions generation is completely automatic, and you will have to 
-rerun the `bashly add comp *` command whenever you change your `bashly.yml` 
-script.
-
-In addition to suggesting subcommands and flags, you can instruct bashly to
-also suggest files, directories, users and more. To do this, add another option
-in your `bashly.yml` on the command you wish to alter:
-
-```yaml
-# bashly.yml
-commands:
-- name: upload
-  help: Upload a file
-  completions: [directory, user]
-
-```
-
-Valid completion additions are:
-
-| Keyword     | Meaning
-|-------------|---------------------
-| `alias`     | Alias names
-| `arrayvar`  | Array variable names
-| `binding`   | Readline key binding names
-| `builtin`   | Names of shell builtin commands
-| `command`   | Command names
-| `directory` | Directory names
-| `disabled`  | Names of disabled shell builtins
-| `enabled`   | Names of enabled shell builtins
-| `export`    | Names of exported shell variables
-| `file`      | File names
-| `function`  | Names of shell functions
-| `group`     | Group names
-| `helptopic` | Help topics as accepted by the help builtin
-| `hostname`  | Hostnames, as taken from the file specified by the HOSTFILE shell variable
-| `job`       | Job names
-| `keyword`   | Shell reserved words
-| `running`   | Names of running jobs
-| `service`   | Service names
-| `signal`    | Signal names
-| `stopped`   | Names of stopped jobs
-| `user`      | User names
-| `variable`  | Names of all shell variables
-
-Note that these are taken from the [Programmable Completion Builtin][compgen], 
-and will simply be added using the `compgen -A action` command.
-
-
-## Real World Examples
-
-- [Rush][rush] - a Personal Package Manager
-- [Alf][alf] - a generator for bash aliases and sub-aliases
-- [git-changelog][git-changelog] - a change log generator
-
-
 ## Contributing / Support
 
 If you experience any issue, have a question or a suggestion, or if you wish
@@ -410,8 +72,6 @@ to contribute, feel free to [open an issue][issues].
 
 
 [issues]: https://github.com/DannyBen/bashly/issues
-[rush]: https://github.com/DannyBen/rush-cli
-[alf]: https://github.com/DannyBen/alf
-[git-changelog]: https://github.com/DannyBen/git-changelog
-[completely]: https://github.com/DannyBen/completely
-[compgen]: https://www.gnu.org/software/bash/manual/html_node/Programmable-Completion-Builtins.html
+[docs]: https://bashly.dannyb.co/
+[examples]: https://github.com/DannyBen/bashly/tree/master/examples#bashly-examples
+

data/lib/bashly/commands/add.rb

@@ -13,7 +13,7 @@ module Bashly
 
       option "-f --force", "Overwrite existing files"
 
-      param "FORMAT", "Output format, can be one of:\n  function : generate a function file to be included in your script.\n  script   : generate a standalone bash completions script\n  yaml     : generate a yaml compatible with 'completely'"
+      param "FORMAT", "Output format, can be one of:\n  function : generate a function file to be included in your script.\n  script   : generate a standalone bash completions script.\n  yaml     : generate a yaml compatible with completely."
       param "OUTPUT", "For the 'comp function' command: Name of the generated function.\nFor the 'comp script' or 'comp yaml' commands: path to output file.\nIn all cases, this is optional and will have sensible defaults."
 
       command "strings", "Copy an additional configuration file to your project, allowing you to customize all the tips and error strings."

data/lib/bashly/concerns/completions.rb

@@ -31,18 +31,15 @@ module Bashly
       flags.map(&:name) + flags.map(&:short)
     end
 
-    def completion_actions
-      completions ? completions.map { |c| "<#{c}>" } : []
-    end
-
     def completion_words(with_version: false)
       trivial_flags = %w[--help -h]
       trivial_flags += %w[--version -v] if with_version
       all = (
         command_names + trivial_flags +
-        completion_flag_names + completion_actions
+        completion_flag_names
       )
 
+      all += completions if completions
       all.compact.uniq.sort
     end
 

data/lib/bashly/models/command.rb

@@ -5,7 +5,7 @@ module Bashly
 
       # Returns the name to be used as an action.
       # - If it is the root command, the action is "root"
-      # - Else, it is all the parents, except the first tone (root) joined
+      # - Else, it is all the parents, except the first one (root) joined
       #   by space. For example, for a command like "docker container run"
       #   the action name is "container run".
       def action_name
@@ -54,6 +54,17 @@ module Bashly
         end
       end
 
+      # Returns true if catch_all is required
+      def catch_all_required?
+        catch_all.is_a?(Hash) and catch_all['required']
+      end
+
+      # Returns a string suitable for catch_all Usage pattern
+      def catch_all_usage
+        return nil unless catch_all
+        catch_all_required? ? catch_all_label : "[#{catch_all_label}]"
+      end
+
       # Returns only the names of the Commands
       def command_names
         commands.map &:name
@@ -92,6 +103,11 @@ module Bashly
         commands.find { |c| c.default }
       end
 
+      # Returns an array of all the default Environment Variables
+      def default_environment_variables
+        environment_variables.select &:default
+      end
+
       # Returns an array of all the default Flags
       def default_flags
         flags.select &:default
@@ -185,7 +201,7 @@ module Bashly
           result << arg.usage_string
         end
         result << "[options]" unless flags.empty?
-        result << "[#{catch_all_label}]" if catch_all
+        result << catch_all_usage if catch_all
         result.join " "
       end
 

data/lib/bashly/templates/lib/config.sh

@@ -17,7 +17,7 @@ config_init() {
   [[ -f "$CONFIG_FILE" ]] || touch "$CONFIG_FILE"
 }
 
-# Get a value from the config
+# Get a value from the config.
 # Usage: result=$(config_get hello)
 config_get() {
   key=$1
@@ -66,7 +66,7 @@ config_set() {
   printf "%b\n" "$output" > "$CONFIG_FILE"
 }
 
-# Delete a key from teh config.
+# Delete a key from the config.
 # Usage: config_del key
 config_del() {
   key=$1
@@ -92,7 +92,7 @@ config_show() {
   cat "$CONFIG_FILE"
 }
 
-# Return an array of the keys in the config file
+# Return an array of the keys in the config file.
 # Usage:
 #
 #   for k in $(config_keys); do
@@ -114,7 +114,7 @@ config_keys() {
   echo "${keys[@]}"
 }
 
-# Returns true if the specified key exists in the config file
+# Returns true if the specified key exists in the config file.
 # Usage:
 #
 #   if config_has_key "key" ; then

data/lib/bashly/templates/strings.yml

@@ -31,3 +31,4 @@ missing_required_environment_variable: "missing required environment variable: %
 missing_dependency: "missing dependency: %{dependency}"
 disallowed_flag: "%{name} must be one of: %{allowed}"
 disallowed_argument: "%{name} must be one of: %{allowed}"
+unsupported_bash_version: "bash version 4 or higher is required"

data/lib/bashly/version.rb

@@ -1,3 +1,3 @@
 module Bashly
-  VERSION = "0.6.0"
+  VERSION = "0.6.4"
 end

data/lib/bashly/views/command/catch_all_filter.erb

@@ -0,0 +1,7 @@
+# :command.catch_all_filter
+<%- if catch_all_required? -%>
+if [[ ${#other_args[@]} -eq 0 ]]; then
+  printf "<%= strings[:missing_required_argument] % { arg: catch_all_label, usage: usage_string } %>\n"
+  exit 1
+fi
+<%- end -%>

data/lib/bashly/views/command/environment_variables_filter.erb

@@ -1,4 +1,9 @@
 # :command.environment_variables_filter
+<%- if default_environment_variables.any? -%>
+<%- default_environment_variables.each do |env_var| -%>
+export <%= env_var.name.upcase %>="${<%= env_var.name.upcase %>:-<%= env_var.default %>}"
+<%- end -%>
+<%- end -%>
 <%- if required_environment_variables.any? -%>
 <%- required_environment_variables.each do |env_var| -%>
 if [[ -z "$<%= env_var.name.upcase %>" ]]; then

data/lib/bashly/views/command/fixed_flags_filter.erb

@@ -16,7 +16,7 @@ case "$1" in
 <%- end -%>
   long_usage=yes
   <%= function_name %>_usage
-  exit 1
+  exit
   ;;
 
 esac

data/lib/bashly/views/command/initialize.erb

@@ -2,7 +2,12 @@
 initialize() {
   version="<%= version %>"
   long_usage=''
-  set -e  
+  set -e
+
+  if [[ "${BASH_VERSINFO:-0}" -lt 4 ]]; then
+    printf "<%= strings[:unsupported_bash_version] -%>\n"
+    exit 1
+  fi
 
 <%= load_user_file("initialize.sh", placeholder: false).indent 2 %>
 }

data/lib/bashly/views/command/parse_requirements.erb

@@ -11,6 +11,7 @@ parse_requirements() {
 <%= render(:required_args_filter).indent 2 %>
 <%= render(:required_flags_filter).indent 2 %>
 <%= render(:parse_requirements_while).indent 2 %>
+<%= render(:catch_all_filter).indent 2 %>
 <%= render(:default_assignments).indent 2 %>
 <%= render(:whitelist_filter).indent 2 %>
 }

data/lib/bashly/views/environment_variable/usage.erb

@@ -1,4 +1,7 @@
 # :environment_variable.usage
 echo "  <%= usage_string extended: true %>"
 printf "<%= help.wrap(76).indent(4).sanitize_for_print %>\n"
+<%- if default -%>
+printf "    <%= strings[:default] % { value: default } -%>\n"
+<%- end -%>
 echo

data/lib/bashly.rb

@@ -5,7 +5,6 @@ if ENV['BYEBUG']
   require 'lp'
 end
 
-requires 'bashly/polyfills'
 requires 'bashly/concerns'
 
 requires 'bashly/settings'

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: bashly
 version: !ruby/object:Gem::Version
-  version: 0.6.0
+  version: 0.6.4
 platform: ruby
 authors:
 - Danny Ben Shitrit
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2021-07-21 00:00:00.000000000 Z
+date: 2021-08-27 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: colsole
@@ -102,7 +102,6 @@ files:
 - lib/bashly/models/environment_variable.rb
 - lib/bashly/models/flag.rb
 - lib/bashly/models/script.rb
-- lib/bashly/polyfills/hash.rb
 - lib/bashly/settings.rb
 - lib/bashly/templates/bashly.yml
 - lib/bashly/templates/lib/colors.sh
@@ -113,6 +112,7 @@ files:
 - lib/bashly/templates/strings.yml
 - lib/bashly/version.rb
 - lib/bashly/views/argument/usage.erb
+- lib/bashly/views/command/catch_all_filter.erb
 - lib/bashly/views/command/command_fallback.erb
 - lib/bashly/views/command/command_filter.erb
 - lib/bashly/views/command/command_functions.erb
@@ -169,7 +169,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.2.16
+rubygems_version: 3.2.25
 signing_key: 
 specification_version: 4
 summary: Bash Command Line Tool Generator

data/lib/bashly/polyfills/hash.rb

@@ -1,12 +0,0 @@
-# :nocov:
-
-# Required for Ruby < 2.4
-if !Dir.respond_to? :empty?
-  class Dir
-    def self.empty?(path_name)
-      exist?(path_name) && (entries(path_name) - ['.', '..']).empty?
-    end
-  end
-end
-
-# :nocov: