toys 0.4.5 → 0.5.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: f92113048faa9971b6ee6523ba02d445a675411532d29c0ee16cc31fc6a58f47
-  data.tar.gz: 15f35f8c92ced516dc646caf4b63b6cd736d5d22539caee830d40a1f69549d8d
+  metadata.gz: 516ab9d472491bb7250ac10e033024dd2e621908836d8e7ccce46d563418d3d3
+  data.tar.gz: 706e194857b09e1f24f2a360d03ba42259b1782284c80f56299bef3d5dc991b4
 SHA512:
-  metadata.gz: 8313128eaa43f9615085613eaa714fbd2f51321d6f48c25bc562649d3b72cc38dc7816e8cca89110a547b1f2f48d8a897543419def4e2c1ac465dac367a9024e
-  data.tar.gz: 381ae7f1311fee5946e179c1ad960c9cacc0a27b2deca5a9df251a9dee971eee2f8562e70ec50781827d83d2defd050d84c8108c8d5445d3f80c09fc5b77fa66
+  metadata.gz: 21ea81146849ffa1549803556ec237af812223b7d3e88ae4f36115ac1ee45ce8795bedbc3b6cbf5168322d557cb85397e89c51195bb8385172ab1bc61b47b24f
+  data.tar.gz: 0c5ec538c871002c01261cfe662ba732f164fb977ed7906460608517f86c0bc16319ba7da3f7e5294ac8aab7e786a5ab0126dbfe7c5ff50d4815ce3514514c8e

data/.yardopts

@@ -1,6 +1,7 @@
 --no-private
 --title=Toys
 --markup=markdown
+--markup-provider redcarpet
 --main=README.md
 ./lib/**/*.rb
 -

data/CHANGELOG.md

@@ -1,5 +1,16 @@
 # Release History
 
+### 0.5.0 / 2018-10-07
+
+* ADDED: Period and colon are recognized as tool path delimiters.
+* ADDED: New rake template that supports loading rake tasks as tools.
+* ADDED: Files named ".preload.rb" and files in a ".preload" directory are loaded before tools are defined.
+* ADDED: Directories named ".data" can contain data files accessible from tools.
+* ADDED: Passing "--tools" displays just the list of subtools of a tool
+* IMPROVED: The tool directive can now take an array as the tool name.
+* IMPROVED: The tool directive can now take an `if_defined` argument.
+* FIXED: Template instantiation was failing if the hosting tool was priority-masked.
+
 ### 0.4.5 / 2018-08-05
 
 * CHANGED: Dropped preload file feature

data/docs/guide.md

@@ -79,6 +79,13 @@ words. Tools are arranged hierarchically. In this case, `system` is a
 **namespace** for tools related to the Toys system, and `version` is one of its
 **subtools**. It prints the current Toys version.
 
+The words in a tool name can be delimited with spaces as shown above, or
+alternately periods or colons. The following commands also invoke the tool
+`system version`:
+
+    toys system.version
+    toys system:version
+
 In the following command:
 
          |TOOL| |ARG|
@@ -433,8 +440,8 @@ an example:
                  long_desc: ["Long descriptions may have multiple lines.",
                              "This is the second line."]
 
-See the [above section on Descriptions](#descriptions) for more information on
-how descriptions are rendered and word wrapped.
+See the [above section on Descriptions](#Tool_Descriptions) for more
+information on how descriptions are rendered and word wrapped.
 
 Because long descriptions may be unwieldly to write as a hash argument in this
 way, Toys provides an alternate syntax for defining arguments using a block.
@@ -477,7 +484,7 @@ and
 [OptionParser::OctalInteger](http://ruby-doc.org/stdlib/libdoc/optparse/rdoc/OptionParser.html#OctalInteger).
 
 You may also create **custom acceptors**. See the
-[section below on Custom Acceptors](#custom-acceptors) for more information.
+[section below on Custom Acceptors](#Custom_Acceptors) for more information.
 
 ### Flags
 
@@ -570,7 +577,7 @@ and
 [OptionParser::OctalInteger](http://ruby-doc.org/stdlib/libdoc/optparse/rdoc/OptionParser.html#OctalInteger).
 
 You may also create **custom acceptors**. See the
-[section below on Custom Acceptors](#custom-acceptors) for more information.
+[section below on Custom Acceptors](#Custom_Acceptors) for more information.
 
 #### Defaults and Handlers
 
@@ -619,7 +626,7 @@ like this:
 Note that both flags affect the same option value, `VERBOSITY`. The first
 increments it each time it appears, and the second decrements it. A tool can
 query this option and get an integer telling the requested verbosity level, as
-you will see [below](#logging-and-verbosity).
+you will see [below](#Logging_and_Verbosity).
 
 #### Descriptions and the Flags DSL
 
@@ -633,7 +640,7 @@ directive. The `desc:` argument takes a single string description, while the
          long_desc: ["Long descriptions may have multiple lines.",
                      "This is the second line."]
 
-See the [above section on Descriptions](#descriptions) for more information on
+See the [above section on Descriptions](#Tool_Descriptions) for more information on
 how descriptions are rendered and word wrapped.
 
 Because long descriptions may be unwieldly to write as a hash argument in this
@@ -659,7 +666,7 @@ your tools.
 
 Note: If you do not define the `run` method for a tool, Toys provides a default
 implementation that displays the tool's help screen. This is typically used for
-namespaces, as we shall see [below](#namespaces-and-subtools). Most tools,
+namespaces, as we shall see [below](#Namespaces_and_Subtools). Most tools,
 however, should define `run`.
 
 Let's revisit the "greet" example we covered earlier.
@@ -824,7 +831,7 @@ than two or three levels of hierarchy can be confusing to use.
 ## Understanding Toys Files
 
 Toys commands are defined in Toys files. We covered the basic syntax for these
-files in the [above section on defining tools](#defining-tools). In this
+files in the [above section on defining tools](#Defining_Tools). In this
 section, we will take a deeper look at what you can do with Toys files.
 
 ### Toys Directories
@@ -929,7 +936,7 @@ in the separate file `.toys/test/unit.rb`.
 Toys also loads index files first before other files in the directory. This
 means they are convenient places to define shared code that can be used by all
 the subtools defined in that directory, as we shall see later in the
-[section on sharing code](#sharing-code).
+[section on sharing code](#Sharing_Code).
 
 ### The Toys Search Path
 
@@ -1047,7 +1054,7 @@ or the
 [Toys::Tool#verbosity method](https://www.rubydoc.info/gems/toys-core/Toys%2FTool:verbosity).
 The verbosity is set to 0 by default. This corresponds to a logger level of
 `WARN`. That is, warnings, errors, and fatals are displayed, while infos and
-debugs are not. However, [as we saw earlier](#standard-flags), most tools
+debugs are not. However, [as we saw earlier](#Standard_Flags), most tools
 automatically respond to the `--verbose` and `--quiet` flags, (or `-v` and
 `-q`), which increment and decrement the verbosity value, respectively. If you
 run a tool with `-v`, the verbosity is incremented to 1, and the logger level
@@ -1076,7 +1083,7 @@ execute, and return a process status object (i.e. 0 for success, and nonzero
 for error). Make sure you handle the exit status. For example, in most cases,
 you should probably exit if the tool you are calling returns a nonzero code.
 
-You may also use the `exec` mixin [described below](#executing-subprocesses) to
+You may also use the `exec` mixin [described below](#Executing_Subprocesses) to
 run a tool in a separate process. This is particularly useful if you need to
 capture or manipulate that tool's input or output.
 
@@ -1084,7 +1091,7 @@ capture or manipulate that tool's input or output.
 
 The methods of [Toys::Tool](https://www.rubydoc.info/gems/toys-core/Toys/Tool)
 are not the only methods available for your tool to call. We
-[saw earlier](#tool-execution-basics) that a tool can define additional methods
+[saw earlier](#Tool_Execution_Basics) that a tool can define additional methods
 that you can use as helpers.
 
 You can also include **mixins**, which are modules that bring in a whole set of
@@ -1109,7 +1116,7 @@ We will look at a few examples of the use of these mixins below. Built-in
 mixins have names that are symbols.
 
 You can also define your own mixins, as we will see in the
-[next section on sharing code](#defining-mixins).
+[upcoming section on defining mixins](#Defining-Mixins).
 
 ### Executing Subprocesses
 
@@ -1167,7 +1174,7 @@ more information, see the
 
 You may also use other third-party gems such as
 [tty](https://github.com/piotrmurach/tty). The section below on
-[useful gems](#useful-gems) provides some examples.
+[useful gems](#Useful_Gems) provides some examples.
 
 ## Sharing Code
 
@@ -1180,7 +1187,7 @@ classes, and constants, that you might define in your tools.
 
 ### Defining Mixins
 
-We [saw earlier](#helper-methods-and-mixins) that you can mix a module (with
+We [saw earlier](#Helper_Methods_and_Mixins) that you can mix a module (with
 all its methods) into your tool using the `include` directive. You can specify
 a module itself, or the name of a built-in mixin such as `:exec` or
 `:terminal`. But you can also define your own mixin using the `mixin`
@@ -1195,7 +1202,7 @@ includes the mixin, in the same way that you can include a Ruby module.
 
 (Note that, unlike full modules, mixins allow only methods to be shared. Mixins
 do not support constants. See the next section on
-[using constants](#using-constants) to learn how Toys handles constants.)
+[using constants](#Using_Constants) to learn how Toys handles constants.)
 
 Here's an example. Suppose you had common setup code that you wanted to share
 among your testing tools.
@@ -1402,7 +1409,7 @@ development, including templates that generate build, test, and documentation
 tools. The `:minitest` template illustrated above is one of these built-in
 templates. Like built-in mixins, built-in template names are always symbols.
 You can read more about them in the next section on using
-[Toys as a Rake replacement](#toys-as-a-rake-replacement).
+[Toys as a Rake replacement](#Toys_as_a_Rake_Replacement).
 
 You may also write your own templates. Here's how...
 
@@ -1509,6 +1516,152 @@ following in their Toys file:
     require "my_analysis"
     expand MyAnalysis::ToysTemplate
 
+### Preloading Ruby Files
+
+For more complicated tools, you might want to write normal Ruby modules and
+classes as helpers. Toys provides a way to write Ruby code outside of its DSL
+and incorporate it into your tool definitions, using "preloaded" files.
+
+A preloaded file is loaded using the standard Ruby `require` mechanism, before
+tools are defined. You can use such files to define Ruby classes, modules, and
+other code that may be used and shared by your tools.
+
+To use preloaded files, you must define your tools inside a
+[Toys directory](#Toys_Directories). Before any tools inside a directory are
+loaded, any file named `.preload.rb` in the directory is automatically
+required. Additionally, any Ruby files inside a subdirectory called `.preload`
+are also automatically required.
+
+For example, take the following directory structure:
+
+    (current directory)
+    |
+    +- .toys/
+       |
+       +- .preload.rb   <-- required first
+       |
+       +- greet.rb   <-- defines "greet" (and subtools)
+       |
+       +- test/
+          |
+          +- .preload/
+          |  |
+          |  +- my_classes.rb  <-- required before unit.rb
+          |  |
+          |  +- my_modules.rb  <-- also required before unit.rb
+          |
+          +- unit.rb   <-- defines "test unit" (and its subtools)
+
+Toys will execute
+
+    require ".toys/.preload.rb"
+
+first before loading any of the tools in the `.toys` directory (or any of its
+subdirectories). Thus, you can define classes used by both the `greet` and the
+`test unit` tool in this file.
+
+Furthermore, Toys will also execute
+
+    require ".toys/test/.preload/my_classes.rb"
+    require ".toys/test/.preload/my_modules.rb"
+
+first before loading any of the tools in the `test` subdirectory. Thus, any
+additional classes needed by `test unit` can be defined in these files.
+
+Either a single `.preload.rb` file or a `.preload` directory, or both, may be
+used. If both are present, the `.preload.rb` file is loaded first before the
+`.preload` directory contents.
+
+### Data Files
+
+If your tools require images, archives, keys, or other such static data, Toys
+provides a convenient place to put data files that can be looked up by tools
+either during definition or runtime.
+
+To use data files, you must define your tools inside a
+[Toys directory](#Toys_Directories). Within the Toys directory, create a
+directory named `.data` and copy your data files there. You may "find" a data
+file using the `find_data` directive in a Toys file, or by calling the
+`find_data` method in a tool. The `find_data` mechanism takes a relative path
+to a file, locates a matching file (or directory) among the data files, and
+returns the full path to that file system object. You may then read the file
+or perform any other operation on it.
+
+For example, take the following directory structure:
+
+    (current directory)
+    |
+    +- .toys/
+       |
+       +- .data
+       |  |
+       |  +- greeting.txt
+       |  |
+       |  +- desc/
+       |     |
+       |     +- short.txt
+       |
+       +- greet.rb   <-- defines "greet" (and subtools)
+
+The data files in `.toys/.data` are available to any tool in the `.toys`
+directory or any of its subdirectories. For example, suppose we want our
+"greet" tool to use the contents of `greeting.txt`. We can call `find_data` to
+read those contents when the tool is executed:
+
+    # greet.rb
+    desc "Print a friendly greeting."
+    optional_arg :whom, default: "world", desc: "Whom to greet."
+    def run
+      greeting = IO.read(find_data("greeting.txt")).strip
+      puts "#{greeting}, #{whom}!"
+    end
+
+You can include directories in the argument to `find_data`. For example, here
+is how to use the `find_data` directive to read the short description from the
+file "desc/short.txt":
+
+    # greet.rb
+    desc IO.read(find_data("desc/short.txt")).strip
+    optional_arg :whom, default: "world", desc: "Whom to greet."
+    def run
+      greeting = IO.read(find_data("greeting.txt")).strip
+      puts "#{greeting}, #{whom}!"
+    end
+
+The `find_data` mechanism will return the "closest" file or directory found.
+In the example below, there is a `desc/short.txt` file in the `.data` directory
+at the top level, but there is also a `desc/short.txt` file in the `.data`
+directory under `test`. Tools under the `test` directory will find the more
+specific data file, while other tools will find the more general file.
+
+    (current directory)
+    |
+    +- .toys/
+       |
+       +- .data
+       |  |
+       |  +- greeting.txt
+       |  |
+       |  +- desc/
+       |     |
+       |     +- short.txt  <-- default description for all tools
+       |
+       +- greet.rb   <-- defines "greet" (and subtools)
+       |
+       +- test/
+          |
+          +- .data
+          |  |
+          |  +- desc/
+          |     |
+          |     +- short.txt  <-- override description for test tools
+          |
+          +- unit.rb   <-- defines "test unit" (and its subtools)
+
+If, however, you find `greeting.txt` from a tool under `test`, it will still
+find the more general `.toys/.data/greeting.txt` file because there is no
+overriding file under `.toys/test/.data`.
+
 ## Using Third-Party Gems
 
 The Ruby community has developed many resources for building command line
@@ -1662,7 +1815,7 @@ directory. Rake is also commonly used for this purpose: you can write a
 "Rakefile" that defines rake tasks scoped to a directory. In many cases, Toys
 can be used as a replacement for Rake. Indeed, the Toys repository itself
 contains a `.toys.rb` file that defines tools for running tests, builds, and so
-forth, instead of a Rakefile that is otherwise often used for this purpose.
+forth, instead of a Rakefile.
 
 This section will explore the differences between Toys and Rake, and describe
 how to use Toys for some of the things traditionally done with Rake.
@@ -1709,15 +1862,77 @@ your build tasks. Rake will continue to be your friend in those cases. However,
 for high level tasks such as "run my tests", "build my YARD documentation", or
 "release my gem", you may find Toys easier to use.
 
+### Using Toys to Invoke Rake Tasks
+
+If you've already written a Rakefile for your project, Toys provides a
+convenient way to invoke your existing Rake tasks using Toys. The built-in
+`:rake` template reads a Rakefile and automatically generates corresponding
+tools.
+
+In the same directory as your Rakefile, create a `.toys.rb` file with the
+following contents:
+
+    # In .toys.rb
+    expand :rake
+
+Now within that directory, if you had a task called `test`, you can invoke it
+with:
+
+    toys test
+
+Similarly, a task named `test:integration` can be invoekd with either of the
+following:
+
+    toys test integration
+    toys test:integration
+
+Rake tasks with arguments are mapped to tool arguments, making it easier to
+invoke those tasks using Toys. For example, consider a Rake task with two
+arguments, defined as follows:
+
+    # In Rakefile
+    task :my_task, [:first, :second] do |task, args|
+      do_something_with args[:first]
+      do_something_else_with args[:second]
+    end
+
+would have to be invoked as follows using rake:
+
+    rake my_task[value1,value2]
+
+You may even need to escape the brackets if you are using a shell that treats
+them specially. Toys will let you pass them as normal command line arguments:
+
+    toys my_task value1 value2
+
+The `:rake` template provides several options. If your Rakefile is named
+something other than `Rakefile` or isn't in the current directory, you can
+pass an explicit path to it when expanding the template:
+
+    # In .toys.rb
+    expand :rake, rakefile_path: "path/to/my_rakefile"
+
+You may also choose to pass arguments as named flags rather than command line
+arguments. Set `:use_flags` when expanding the template:
+
+    # In .toys.rb
+    expand :rake, use_flags: true
+
+Now with this option, to pass arguments to the tool, use the argument names as
+flags:
+
+    toys my_task --first=value1 --second=value2
+
 ### From Rakefiles to Toys Files
 
-If you want to migrate some of your project's build tasks from Rake to Toys,
-there are some common patterns.
+Invoking Rake tasks using Toys is an easy first step, but eventually you will
+likely want to migrate some of your project's build tasks from Rake to Toys.
+The remainder of this section describes the common patterns and features Toys
+provides for writing build tasks that are traditionally done with Rake.
 
-When you use Rake for these tasks, you will typically require a particular file
-from your Rakefile, and/or write some code. Different tools will have different
-mechanisms for generating tasks. For example, a test task might be defined like
-this:
+Many common Rake tasks can be generated using code provided by either Rake or
+the third party library. Different libraries provide different mechanisms for
+task generation. For example, a test task might be defined like this:
 
     require "rake/testtask"
     Rake::TestTask.new do |t|

data/lib/toys.rb

@@ -30,10 +30,13 @@
 ;
 
 ##
-# Toys is a Ruby library and command line tool that lets you build your own
-# command line suite of tools (with commands and subcommands) using a Ruby DSL.
-# You can define commands globally or configure special commands scoped to
-# individual directories.
+# Toys is a configurable command line tool. Write commands in config files
+# using a simple DSL, and Toys will provide the command line binary and take
+# care of all the details such as argument parsing, online help, and error
+# reporting. Toys is designed for software developers, IT professionals, and
+# other power users who want to write and organize scripts to automate their
+# workflows. It can also be used as a Rake replacement, providing a more
+# natural command line interface for your project's build tasks.
 #
 module Toys
   ##

data/lib/toys/standard_cli.rb

@@ -61,12 +61,36 @@ module Toys
     #
     INDEX_FILE_NAME = ".toys.rb"
 
+    ##
+    # Standard preload directory name in a toys configuration
+    # @return [String]
+    #
+    PRELOAD_DIRECTORY_NAME = ".preload"
+
+    ##
+    # Standard preload file name in a toys configuration
+    # @return [String]
+    #
+    PRELOAD_FILE_NAME = ".preload.rb"
+
+    ##
+    # Standard data directory name in a toys configuration
+    # @return [String]
+    #
+    DATA_DIRECTORY_NAME = ".data"
+
     ##
     # Name of standard toys binary
     # @return [String]
     #
     BINARY_NAME = "toys"
 
+    ##
+    # Delimiter characters recognized
+    # @return [String]
+    #
+    EXTRA_DELIMITERS = ":."
+
     ##
     # Short description for the standard root tool
     # @return [String]
@@ -78,9 +102,10 @@ module Toys
     # @return [String]
     #
     DEFAULT_ROOT_LONG_DESC =
-      "Toys is your personal command line tool. You can add to the list of commands below by" \
-      " writing scripts in Ruby using a simple DSL, and Toys will organize and document them" \
-      " and make them available globally or scoped to specific directories that you choose." \
+      "Toys is your personal command line tool. You can write commands using a simple Ruby DSL," \
+      " and Toys will automatically organize them, parse arguments, and provide documentation." \
+      " Tools can be global or scoped to specific directories. You can also use Toys instead of" \
+      " Rake to provide build and maintenance scripts for your projects." \
       " For detailed information, see https://www.rubydoc.info/gems/toys"
 
     ##
@@ -103,6 +128,10 @@ module Toys
         config_dir_name: CONFIG_DIR_NAME,
         config_file_name: CONFIG_FILE_NAME,
         index_file_name: INDEX_FILE_NAME,
+        preload_file_name: PRELOAD_FILE_NAME,
+        preload_directory_name: PRELOAD_DIRECTORY_NAME,
+        data_directory_name: DATA_DIRECTORY_NAME,
+        extra_delimiters: EXTRA_DELIMITERS,
         middleware_stack: default_middleware_stack,
         template_lookup: default_template_lookup
       )
@@ -154,6 +183,7 @@ module Toys
           :show_help,
           help_flags: true,
           usage_flags: true,
+          list_flags: true,
           recursive_flags: true,
           search_flags: true,
           default_recursive: true,

data/lib/toys/templates/rake.rb

@@ -0,0 +1,123 @@
+# frozen_string_literal: true
+
+# Copyright 2018 Daniel Azuma
+#
+# All rights reserved.
+#
+# Redistribution and use in source and binary forms, with or without
+# modification, are permitted provided that the following conditions are met:
+#
+# * Redistributions of source code must retain the above copyright notice,
+#   this list of conditions and the following disclaimer.
+# * Redistributions in binary form must reproduce the above copyright notice,
+#   this list of conditions and the following disclaimer in the documentation
+#   and/or other materials provided with the distribution.
+# * Neither the name of the copyright holder, nor the names of any other
+#   contributors to this software, may be used to endorse or promote products
+#   derived from this software without specific prior written permission.
+#
+# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+# AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+# IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+# ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
+# LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
+# CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
+# SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
+# INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
+# CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
+# ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
+# POSSIBILITY OF SUCH DAMAGE.
+;
+
+module Toys
+  module Templates
+    ##
+    # A template that generates tools matching a rakefile.
+    #
+    class Rake
+      include Template
+
+      ##
+      # Default path to the Rakefile.
+      # @return [String]
+      #
+      DEFAULT_RAKEFILE_PATH = "Rakefile"
+
+      ##
+      # Create the template settings for the rake template.
+      #
+      # @param [String,Array<String>,nil] gem_version Version requirements for
+      #     the rake gem. Defaults to nil, indicating no version requirement.
+      # @param [String] rakefile_path Path to the Rakefile. Defaults to
+      #     {DEFAULT_RAKEFILE_PATH}.
+      # @param [Boolean] only_described Tools are generated only for rake tasks
+      #     with descriptions. Default is false.
+      # @param [Boolean] use_flags Generated tools use flags instead of
+      #     positional arguments to pass arguments to rake tasks. Default is
+      #     false.
+      #
+      def initialize(gem_version: nil,
+                     rakefile_path: nil,
+                     only_described: false,
+                     use_flags: false)
+        @gem_version = gem_version
+        @rakefile_path = rakefile_path || DEFAULT_RAKEFILE_PATH
+        @only_described = only_described
+        @use_flags = use_flags
+      end
+
+      attr_accessor :gem_version
+      attr_accessor :rakefile_path
+      attr_accessor :only_described
+      attr_accessor :use_flags
+
+      to_expand do |template|
+        gem "rake", *Array(template.gem_version)
+        require "rake"
+        ::Rake::TaskManager.record_task_metadata = true
+        rake = ::Rake::Application.new
+        ::Rake.application = rake
+        ::Rake.load_rakefile(template.rakefile_path)
+        rake.tasks.each do |task|
+          comments = task.full_comment.to_s.split("\n")
+          next if comments.empty? && template.only_described
+          tool(task.name.split(":"), if_defined: :ignore) do
+            unless comments.empty?
+              desc(comments.first)
+              long_desc(*comments)
+            end
+            if template.use_flags
+              task.arg_names.each do |arg|
+                specs = Templates::Rake.flag_specs(arg)
+                flag(arg, *specs) unless specs.empty?
+              end
+              to_run do
+                args = task.arg_names.map { |arg| self[arg] }
+                task.invoke(*args)
+              end
+            else
+              task.arg_names.each do |arg|
+                optional_arg(arg)
+              end
+              to_run do
+                task.invoke(*args)
+              end
+            end
+          end
+        end
+      end
+
+      ## @private
+      def self.flag_specs(arg)
+        name = arg.to_s.gsub(/\W/, "").downcase
+        specs = []
+        unless name.empty?
+          specs << "--#{name}=VALUE"
+          name2 = name.tr("_", "-")
+          specs << "--#{name2}=VALUE" unless name2 == name
+        end
+        specs
+      end
+    end
+  end
+end

data/lib/toys/version.rb

@@ -34,5 +34,5 @@ module Toys
   # Current version of the Toys command line binary
   # @return [String]
   #
-  VERSION = "0.4.5"
+  VERSION = "0.5.0"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: toys
 version: !ruby/object:Gem::Version
-  version: 0.4.5
+  version: 0.5.0
 platform: ruby
 authors:
 - Daniel Azuma
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2018-08-06 00:00:00.000000000 Z
+date: 2018-10-08 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: toys-core
@@ -16,14 +16,28 @@ dependencies:
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 0.4.5
+        version: 0.5.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 0.4.5
+        version: 0.5.0
+- !ruby/object:Gem::Dependency
+  name: highline
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '2.0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '2.0'
 - !ruby/object:Gem::Dependency
   name: minitest
   requirement: !ruby/object:Gem::Requirement
@@ -66,34 +80,48 @@ dependencies:
     - - "~>"
       - !ruby/object:Gem::Version
         version: '5.2'
+- !ruby/object:Gem::Dependency
+  name: redcarpet
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '3.4'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '3.4'
 - !ruby/object:Gem::Dependency
   name: rubocop
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.58.2
+        version: 0.59.1
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.58.2
+        version: 0.59.1
 - !ruby/object:Gem::Dependency
   name: yard
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.9.14
+        version: 0.9.16
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.9.14
+        version: 0.9.16
 description: Toys is a configurable command line tool. Write commands in config files
   using a simple DSL, and Toys will provide the command line binary and take care
   of all the details such as argument parsing, online help, and error reporting. Toys
@@ -121,6 +149,7 @@ files:
 - lib/toys/templates/clean.rb
 - lib/toys/templates/gem_build.rb
 - lib/toys/templates/minitest.rb
+- lib/toys/templates/rake.rb
 - lib/toys/templates/rdoc.rb
 - lib/toys/templates/rubocop.rb
 - lib/toys/templates/yardoc.rb
@@ -128,7 +157,11 @@ files:
 homepage: https://github.com/dazuma/toys
 licenses:
 - BSD-3-Clause
-metadata: {}
+metadata:
+  changelog_uri: https://github.com/dazuma/toys/blob/master/toys/CHANGELOG.md
+  source_code_uri: https://github.com/dazuma/toys
+  bug_tracker_uri: https://github.com/dazuma/toys/issues
+  documentation_uri: https://www.rubydoc.info/gems/toys
 post_install_message: 
 rdoc_options: []
 require_paths: