Fix unhandled_handler configuration

Custom unhandled_handler configuration fix. It wouldn't let you set a custom one as the validation was checking for `is_a?` instead of `<`
jusleg · Mar 25, 2019 · 45586af · 45586af
1 parent 8902d96
commit 45586af
Show file tree

Hide file tree

Showing 4 changed files with 8 additions and 4 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,4 +1,8 @@
-##V0.1.3
+## V0.1.4
+
+Custom unhandled_handler configuration fix. It wouldn't let you set a custom one as the validation was checking for `is_a?` instead of `<`
+
+## V0.1.3
 Added `remove_unhandled_handler` as a configuration option to disable the unhandled handler.
 
 ## V0.1.2

diff --git a/Gemfile.lock b/Gemfile.lock
@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    slackify (0.1.3)
+    slackify (0.1.4)
       rails
       slack-ruby-client
 

diff --git a/lib/slackify/configuration.rb b/lib/slackify/configuration.rb
@@ -18,7 +18,7 @@ def initialize
 
     def unhandled_handler=(handler)
       raise Exceptions::InvalidHandler, "#{handler.class} is not a subclass of Slackify::Handlers::Base" unless
-        handler.is_a?(Handlers::Base)
+        handler < Handlers::Base
 
       @unhandled_handler = handler
     end

diff --git a/slackify.gemspec b/slackify.gemspec
@@ -2,7 +2,7 @@
 
 Gem::Specification.new do |s|
   s.name        = 'slackify'
-  s.version     = '0.1.3'
+  s.version     = '0.1.4'
   s.date        = '2019-03-17'
   s.summary     = 'Slackbot framework for Rails using the Events API'
   s.description = 'Slackbot framework for Rails using the Events API. Supports events, interactive messages and slash commands.'