ianwhite-hark 0.0.5 → 0.0.6

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: a312e8d34fdb0a88013aa0d4602addb244719b35
-  data.tar.gz: 19ec8e5b542f72aaa806bc88a55faa276b275ad7
+  metadata.gz: 6c1768749a71703d7f3a754773c0dda1b9b9c754
+  data.tar.gz: c704b92cd229dc37ecb44a0fa5daff446b64b313
 SHA512:
-  metadata.gz: ad050f9e915f633cbbdd082aed1f6d1e6057f006b44614bc38e760b742b73540444b187f09189d1323efaa2cdbace4514e57a2ac70710db5aa29338cfe93d14a
-  data.tar.gz: 0291b41c2e65a84190aa8e58d3ba68bc0dd61d1b2dc0bfd5ddde32e5410dae1dac020755571c1187614bf9982de897bb8a1391cef2cabacf55fa23cb3f9dac95
+  metadata.gz: 3da05565f8c13dc4d477441f48be5cb746797f6e854af8152c09326b564cd2e6010e177ddaf5c2832472430fec6d7825f2e21665c096ac8854bece6cf22adb4e
+  data.tar.gz: 397d7d99fe5936cca9661fc7e0eb00ef8bbcf484f74f3b04c4e029cf7fcd880dbe2efc6a5f938b0bdc63f8070c869a0bbb5ca9bc2cbdff5e4828925260c95b22

data/History.md

@@ -1,5 +1,9 @@
 # History
 
+## 0.0.6
+
+* remove Kernel#to_hark
+
 ## 0.0.5
 
 * ruby 1.8.7 compat

data/README.md

@@ -42,7 +42,7 @@ You can pass a symbol and block
 
 The following methods are more suitable for a listener with multiple messages.
 
-A hash with callables as keys
+A hash with callables as values
 
     hark(
       created: ->(user) { redirect_to(user, notice: "You have signed up!") },
@@ -50,7 +50,7 @@ A hash with callables as keys
     )
 
     # assuming some methods for rendering and redirecting exist on the controller
-    hash created: method(:redirect_to_user), invalid: method(:render_new)
+    hark(created: method(:redirect_to_user), invalid: method(:render_new))
 
 Or, a 'respond_to' style block
 
@@ -99,9 +99,15 @@ Combine with any object that support the same protocol
     logger = UserLogger.new # responds to :created
     listener = listener.hark(logger)
 
+Turn any object into a listener, adding new methods as we go
+
+    hark UserLogger.new do |on|
+      on.created {|user| Emailer.send_welcom_email(user) }
+    end
+
 Now, when listener is sent #created, all create handlers are called.
 
-### Sugar: #hearken
+### Sugar: `Kernel#hearken`
 
 Because of the precedence of the block operator, constructing ad-hoc listeners requires
 you to insert some parens, which might be seen as unsightly, e.g:
@@ -118,7 +124,7 @@ You may use Kernerl#hearken to create an ad-hoc listener using a passed block as
       on.invalid_item {|item| redirect_to item, error: "Item not evaluable" }
     end
 
-If you want to combine listeners with an ad-hoc blokc, you may pass a 0-arity block that is
+If you want to combine listeners with an ad-hoc block, you may pass a 0-arity block that is
 yielded as the listener
 
     seller.hearken :request_valuation, item do

data/lib/hark/core_ext.rb

@@ -3,10 +3,6 @@ module Kernel
     Hark.from *args, &block
   end
 
-  def to_hark *args, &block
-    hark self, *args, &block
-  end
-
   def hearken method, *args, &block
     listener = (block.arity == 1) ? hark(&block) : block.call
     send method, *args + [listener]

data/lib/hark/version.rb

@@ -1,3 +1,3 @@
 module Hark
-  VERSION = "0.0.5"
+  VERSION = "0.0.6"
 end

data/spec/hark_spec.rb

@@ -97,12 +97,6 @@ describe Hark do
     it_should_behave_like "a success/failure hark listener"
   end
 
-  describe "object.to_hark" do
-    let(:listener) { PlainListener.new(transcript).to_hark }
-
-    it_should_behave_like "a success/failure hark listener"
-  end
-
   describe "combine two listeners together" do
     let(:logger) { hark(:signup_user) {|user| transcript << "User #{user} signed up" } }
     let(:emailer) { hark(:signup_user) {|user| transcript << "Emailed #{user}" } }

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: ianwhite-hark
 version: !ruby/object:Gem::Version
-  version: 0.0.5
+  version: 0.0.6
 platform: ruby
 authors:
 - Ian White