bales 0.1.2 → 0.1.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
-SHA1:
-  metadata.gz: 17750f3056694dcabc3be1c2ac111978e179043f
-  data.tar.gz: b6087e538fd4eccb2e614b1dbd539cf4058b5e90
+SHA256:
+  metadata.gz: b6ada6a857baba9d741859d2ec38d4992e6b9e4b409dd3bb7d0aacce7a6b129b
+  data.tar.gz: 1cbc31b944a5bd783aa563d36477bc15bcabaa5a44d7d6a7f03a586d7d02fd3e
 SHA512:
-  metadata.gz: 05e0241f93ac005d784ca7d66bc806de2e5ef609c947bf69c1cdbbd338512f6c6170697f47561a6476ac40084e02a958caf1f3da1cba73fb230a575de5347c51
-  data.tar.gz: 31421e16c924c9dfc59318117c9c597f51a31925c7b75bc43248613fa4505f57888cdb0f33e7eb456ab7c5fcdac76f416e5ca158404836e99ae3d20a978b8511
+  metadata.gz: 2c4b688015b19d0b11a110729ec6b955e6c11e2ca3cf01f2bec922a9aa03203798bd34fe1efb84f599c89e9cc235939d19e812057348b508b6abf1ff230d7b93
+  data.tar.gz: 1c52425d3d50315b2fcf93d78a603bc47df4a2afa083a4646c92edfad7289fb0e7f11e4e6b421035719cae1a2b81267035581404ebfda511241e2145b8b65a84

data/README.md

@@ -44,7 +44,7 @@ module SimpleApp
         if victims.none?
           puts "You have been smacked#{suffix}."
         else
-          puts "#{victim} has been smacked#{suffix}."
+          victims.each {|v| puts "#{v} has been smacked#{suffix}."}
         end
       end
     end
@@ -67,7 +67,8 @@ end
 SimpleApp::Application.parse_and_run
 ```
 
-And like this (assuming the above script lives in `/usr/local/bin/simple-app`)!
+And like this (assuming the above script lives in
+`/usr/local/bin/simple-app`)!
 
 ```
 $ simple-app
@@ -92,54 +93,95 @@ Bruce has been smacked with a fish.
 ## So how does it work?
 
 * Come up with a name for your app, like `MyApp`
-* Create an `Application` class under that namespace which inherits from `Bales::Application`
+
+* Create an `Application` class under that namespace which inherits
+  from `Bales::Application`
+
 * Use the DSL (or define classes manually, if that's your thing)
 
-Basically, a Bales app is just a bunch of classes with some fairy dust that turns them into runnable commands.  Bales will check the namespace that your subclass of `Bales::Application` lives in for a `Command` namespace, then search there for available commands.
+Basically, a Bales app is just a bunch of classes with some fairy dust
+that turns them into runnable commands.  Bales will check the
+namespace that your subclass of `Bales::Application` lives in for a
+`Command` namespace, then search there for available commands.
 
 The application has a few available DSL-ish functions for you to play with.
 
-* `version`: sets your app's version number.  If you use semantic versioning, you can query this with the `major_version`, `minor_version`, and `patch_level` class methods.
-* `command "foo" { ... }`: defines a subcommand called "foo", which turns into a class called `MyApp::Command::Foo` (if you picked the name `MyApp` above).  If you provide a block, said block will be evaluated in the class' context (see below for things you can do in said context).
+* `version`: sets your app's version number.  If you use semantic
+  versioning, you can query this with the `major_version`,
+  `minor_version`, and `patch_level` class methods.
 
-Meanwhile, commands *also* have some DSL-ish functions to play around with.
+* `command "foo" { ... }`: defines a subcommand called "foo", which
+  turns into a class called `MyApp::Command::Foo` (if you picked the
+  name `MyApp` above).  If you provide a block, said block will be
+  evaluated in the class' context (see below for things you can do in
+  said context).
 
-* `option`: defines a command-line option, like `--verbose` or `-f` or something.  It takes the name of the option (which becomes a key in your command's options hash) and some named parameters:
-  * `:type`: a valid Ruby class, like `String`.  For a boolean, you should provide either `TrueClass` or `FalseClass`, which - when set - will set the option in question to `true` or `false` (respectively).
-  * `:short_form`: a short flag, like `'-v'`.  You must specify this if you want a short flag.
-  * `:long_form`: a long flag, like `'--verbose'`.  This will be created from the option's name if you don't override it here.
-  * `:description`: a quick description of the option, like `"Whether or not to be verbose"`.
-* `action`: defines what the command should do when it's called.  This is provided in the form of a block.  Said block should accept two arguments (an array of arguments and a hash of options), though you don't *have* to name them with pipes and stuff if you know that your command won't take any arguments or options.
-* `description`: sets a long description of what your command does.  Should be a string.
-* `summary`: sets a short description of what your command does.  Should be a string.  Should also be shorter than `:description`, though this isn't strictly necessary.
+Meanwhile, commands *also* have some DSL-ish functions to play around with.
 
-Some of the command functions (`option`, `action`, `description`, `summary`) can also be used from within the application class; doing so will define and configure a "root command", which is what is run if you run your app without any arguments.
+* `option`: defines a command-line option, like `--verbose` or `-f` or
+  something.  It takes the name of the option (which becomes a key in
+  your command's options hash) and some named parameters:
+
+  * `:type`: a valid Ruby class, like `String`.  For a boolean, you
+    should provide either `TrueClass` or `FalseClass`, which - when
+    set - will set the option in question to `true` or `false`
+    (respectively).
+  
+  * `:short_form`: a short flag, like `'-v'`.  You must specify this
+    if you want a short flag.
+  
+  * `:long_form`: a long flag, like `'--verbose'`.  This will be
+    created from the option's name if you don't override it here.
+  
+  * `:description`: a quick description of the option, like `"Whether
+    or not to be verbose"`.
+  
+* `action`: defines what the command should do when it's called.  This
+  is provided in the form of a block.  Said block should accept two
+  arguments (an array of arguments and a hash of options), though you
+  don't *have* to name them with pipes and stuff if you know that your
+  command won't take any arguments or options.
+
+* `description`: sets a long description of what your command does.
+  Should be a string.
+
+* `summary`: sets a short description of what your command does.
+  Should be a string.  Should also be shorter than `:description`,
+  though this isn't strictly necessary.
+
+Some of the command functions (`option`, `action`, `description`,
+`summary`) can also be used from within the application class; doing
+so will define and configure a "root command", which is what is run if
+you run your app without any arguments.
 
 ## What can this thing already do?
 
 * Create a working command-line app
-* Automatically produce subcommands (recursively, in fact) based on the namespaces of the corresponding `Bales::Command` subclasses
+
+* Automatically produce subcommands (recursively, in fact) based on
+  the namespaces of the corresponding `Bales::Command` subclasses
+
 * Provide a DSL defining commands and options
 
 ## What might this thing someday do in the future?
 
 * Provide some helpers to wrap things like HighLine, curses, etc.
-* Provide some additional flexibility in how options are specified without requiring users to completely reimplement a command's option parsing functions
+
+* Provide some additional flexibility in how options are specified
+  without requiring users to completely reimplement a command's option
+  parsing functions
 
 ## What kind of a silly name is "Bales", anyway?
 
-It's shamelessly stolen^H^H^H^H^H^Hborrowed from Jason R. Clark's "Testing the Multiverse" talk at Ruby on Ales 2015 (which, if you haven't watched, you [totally should](http://confreaks.tv/videos/roa2015-testing-the-multiverse)).  Sorry, Jason.  Hope you don't mind.
+It's shamelessly stolen^H^H^H^H^H^Hborrowed from Jason R. Clark's
+"Testing the Multiverse" talk at Ruby on Ales 2015 (which, if you
+haven't watched, you [totally
+should](http://confreaks.tv/videos/roa2015-testing-the-multiverse)).
+Sorry, Jason.  Hope you don't mind.
 
-Ironically enough, despite ripping off the name from a talk about Ruby testing, Bales currently lacks any formal test suite.  Hm...
+Ironically enough, despite ripping off the name from a talk about Ruby
+testing, Bales currently lacks any formal test suite.  Hm...
 
 ## What's the license?
 
-MIT License
-
-Copyright (c) 2015 Ryan S. Northrup
-
-Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+MIT License; see COPYING for details.

data/lib/bales/application.rb

@@ -157,6 +157,11 @@ module Bales
     # command to run and its arguments/options, then runs the command.
     def self.parse_and_run(argv=ARGV)
       command, args, opts = parse argv
+      # OptionParser includes nil values for missing options, so we
+      # need to make sure those don't clobber the command's defaults.
+      command.method(:run).parameters.select {|p| p[0] == :key}.map do |p|
+        opts.delete p[1] if opts[p[1]].nil?
+      end
       run command, *args, **opts
     end
 

data/lib/bales/version.rb

@@ -1,3 +1,3 @@
 module Bales
-  VERSION="0.1.2"
+  VERSION="0.1.3"
 end

metadata

@@ -1,18 +1,18 @@
 --- !ruby/object:Gem::Specification
 name: bales
 version: !ruby/object:Gem::Version
-  version: 0.1.2
+  version: 0.1.3
 platform: ruby
 authors:
 - Ryan S. Northrup
-autorequire: 
+autorequire:
 bindir: bin
 cert_chain: []
-date: 2015-09-05 00:00:00.000000000 Z
+date: 2020-10-26 00:00:00.000000000 Z
 dependencies: []
 description: A framework for building command-line applications
 email:
-- rnorthrup@newleaders.com
+- northrup@yellowapple.us
 executables: []
 extensions: []
 extra_rdoc_files: []
@@ -27,24 +27,23 @@ homepage: http://github.com/YellowApple/bales
 licenses:
 - MIT
 metadata: {}
-post_install_message: 
+post_install_message:
 rdoc_options: []
 require_paths:
 - lib
 required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
-  - - '>='
+  - - ">="
     - !ruby/object:Gem::Version
       version: '0'
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
-  - - '>='
+  - - ">="
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubyforge_project: 
-rubygems_version: 2.4.8
-signing_key: 
+rubygems_version: 3.1.2
+signing_key:
 specification_version: 4
 summary: Ruby on Bales
 test_files: []