toys 0.4.4 → 0.4.5

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: b139a0c2557f3b2d2c1d60b312601bd5c3b3961654e750ccab125df55e281655
-  data.tar.gz: bf69d3a6ec5bd83db10e4c8b8e8bf00850cb1e0ab1565ade586c034bc1e667d2
+  metadata.gz: f92113048faa9971b6ee6523ba02d445a675411532d29c0ee16cc31fc6a58f47
+  data.tar.gz: 15f35f8c92ced516dc646caf4b63b6cd736d5d22539caee830d40a1f69549d8d
 SHA512:
-  metadata.gz: e91e87e3e305e77745f13bcabca141efeddae84ac036d14a8289d7d0a517f4ccbb7f80da6f1e9304018aa45cc7c39582282ba51a9ed92d19a6eeee0852b61f6e
-  data.tar.gz: 7f8b4c1875a2a913bed9d136e5c88c6c52c25406035bd1aa284df0dd840687ea300891b001dcb94f1b94aab15f8cc55ccf97cdca381c55d9ece0611b33d908aa
+  metadata.gz: 8313128eaa43f9615085613eaa714fbd2f51321d6f48c25bc562649d3b72cc38dc7816e8cca89110a547b1f2f48d8a897543419def4e2c1ac465dac367a9024e
+  data.tar.gz: 381ae7f1311fee5946e179c1ad960c9cacc0a27b2deca5a9df251a9dee971eee2f8562e70ec50781827d83d2defd050d84c8108c8d5445d3f80c09fc5b77fa66

data/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Release History
 
+### 0.4.5 / 2018-08-05
+
+* CHANGED: Dropped preload file feature
+
 ### 0.4.4 / 2018-07-21
 
 * FIXED: Utils::Exec wasn't closing streams after copying.

data/README.md

@@ -19,7 +19,7 @@ https://www.rubydoc.info/gems/toys-core
 
 Here's a five-minute tutorial to get a feel of what Toys can do.
 
-### Install toys
+### Install Toys
 
 Install the **toys** gem using:
 
@@ -114,9 +114,9 @@ you find the script you need.
 
 Toys can also be used to share scripts. For example, it can be used instead of
 Rake to provide build and test scripts for a project—tools that, unlike Rake
-tasks, can be invoked and passed arguments using familiar unix command line
-arguments and flags. The Toys github repo itself comes with Toys config files
-instead of Rakefiles.
+tasks, can be invoked and passed arguments and flags using familiar unix
+command line conventions. The Toys github repo itself comes with Toys config
+files instead of Rakefiles.
 
 ## License
 

data/builtins/system.rb

@@ -62,7 +62,7 @@ tool "update" do
       latest_version = ::Gem::Version.new($1)
       cur_version = ::Gem::Version.new(::Toys::VERSION)
       if latest_version > cur_version
-        prompt = "Update Toys from #{cur_version} to #{latest_version}?"
+        prompt = "Update Toys from #{cur_version} to #{latest_version}? "
         exit(1) unless yes || confirm(prompt, default: true)
         result = terminal.spinner(leading_text: "Installing Toys version #{latest_version}... ",
                                   final_text: "Done.\n") do

data/docs/guide.md

@@ -1740,7 +1740,8 @@ can use either or both tools, depending on your needs.
 
 Toys provides a built-in template for minitest, called `:minitest`. It is
 implemented by the template class {Toys::Templates::Minitest}, and it uses the
-minitest gem, which is provided with most recent versions of Ruby.
+minitest gem, which is provided with most recent versions of Ruby. The
+following directive uses the minitest template to create a tool called `test`:
 
     expand :minitest, files: ["test/test*.rb"], libs: ["lib", "ext"]
 
@@ -1748,7 +1749,8 @@ See the {Toys::Templates::Minitest} documentation for details on the various
 options.
 
 If you want to enforce code style using the "rubocop" gem, you can use the
-built-in `:rubocop` template:
+built-in `:rubocop` template. The following directive uses this template to
+create a tool called `rubocop`:
 
     expand :rubocop
 
@@ -1759,9 +1761,12 @@ options.
 
 The `:gem_build` built-in template can generate a variety of build and release
 tools for gems, and is a useful alternative to the Rake tasks provided by
-bundler. It is implemented by {Toys::Templates::GemBuild}.
+bundler. It is implemented by {Toys::Templates::GemBuild}. The following
+directive uses this template to create a tool called `build`:
 
-Expanding `:gem_build` by default looks for a gemspec file in the current
+    expand :gem_build
+
+The `:gem_build` template by default looks for a gemspec file in the current
 directory, and builds that gem into a `pkg` directory. You can also build a
 specific gem if you have multiple gemspec files.
 
@@ -1775,7 +1780,7 @@ your gem:
 See the {Toys::Templates::GemBuild} documentation for details on the various
 options for build tools.
 
-To generate a "clean" tool, you can use the `:clean` built-in template. For
+To create a "clean" tool, you can use the `:clean` built-in template. For
 example:
 
     expand :clean, paths: ["pkg", "doc", "tmp"]
@@ -1791,7 +1796,7 @@ Both templates provide a variety of options for controlling documentation
 generation. See {Toys::Templates::Rdoc} and {Toys::Templates::Yardoc} for
 detailed information.
 
-Here's an example for YARD:
+Here's an example for YARD, creating a tool called `yardoc`:
 
     expand :yardoc, protected: true, markup: "markdown"
 
@@ -1814,6 +1819,8 @@ into the gem source repo with minimal or no modifications. Indeed, it is
 nearly identical to the Toys files provided for the **toys** and **toys-core**
 gems themselves.
 
+    # This file is .toys.rb
+
     # A "clean" tool that cleans out gem builds (from the pkg directory), and
     # documentation builds (from doc and .yardoc)
     expand :clean, paths: ["pkg", "doc", ".yardoc"]
@@ -1843,7 +1850,7 @@ gems themselves.
     # credentials.
     expand :gem_build, name: "release", push_gem: true
 
-    # Now we have a full CI tool. It runs the test, rubocop, and yardoc tools
+    # Now we create a full CI tool. It runs the test, rubocop, and yardoc tools
     # and checks for errors. This tool could be invoked from Travis-CI or
     # similar CI system.
     tool "ci" do

data/lib/toys/standard_cli.rb

@@ -61,12 +61,6 @@ module Toys
     #
     INDEX_FILE_NAME = ".toys.rb"
 
-    ##
-    # Standard toys preload file name
-    # @return [String]
-    #
-    PRELOAD_FILE_NAME = ".preload.rb"
-
     ##
     # Name of standard toys binary
     # @return [String]
@@ -109,7 +103,6 @@ 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,
         middleware_stack: default_middleware_stack,
         template_lookup: default_template_lookup
       )

data/lib/toys/version.rb

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

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: toys
 version: !ruby/object:Gem::Version
-  version: 0.4.4
+  version: 0.4.5
 platform: ruby
 authors:
 - Daniel Azuma
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2018-07-22 00:00:00.000000000 Z
+date: 2018-08-06 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: toys-core
@@ -16,14 +16,14 @@ dependencies:
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 0.4.4
+        version: 0.4.5
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 0.4.4
+        version: 0.4.5
 - !ruby/object:Gem::Dependency
   name: minitest
   requirement: !ruby/object:Gem::Requirement
@@ -72,14 +72,14 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.57.2
+        version: 0.58.2
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.57.2
+        version: 0.58.2
 - !ruby/object:Gem::Dependency
   name: yard
   requirement: !ruby/object:Gem::Requirement