slackify 0.1.3 → 0.1.4
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/CHANGELOG.md +5 -1
- data/lib/slackify/configuration.rb +1 -1
- metadata +1 -1
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA256:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 481a11f7bd67bbd0dade00117995381beb8719b0aba7f4b886372be0fb169d57
|
4
|
+
data.tar.gz: 6d2fad59ffe6938d3bf0f3ba9bf754218faf1cfdeb7f64ed3fd5c586535f465f
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: eec68d6c75d8537cc74036921025d68d14475d5f7f84b3d50d918d33a4f5dec96e2b2080956da0bf52717a24ee882282fd9eaced48f00abfefc30df843d7c0af
|
7
|
+
data.tar.gz: 6e9888657a4a3ec71b86ed7714f21cfc275b9b1e90d0d1136ecba01dfc41853e9cc8b2a0dc58c15f8d8cbc35c3df77d6ea183190add7a2149b2bd759852ba3c2
|
data/CHANGELOG.md
CHANGED
@@ -1,4 +1,8 @@
|
|
1
|
-
##V0.1.
|
1
|
+
## V0.1.4
|
2
|
+
|
3
|
+
Custom unhandled_handler configuration fix. It wouldn't let you set a custom one as the validation was checking for `is_a?` instead of `<`
|
4
|
+
|
5
|
+
## V0.1.3
|
2
6
|
Added `remove_unhandled_handler` as a configuration option to disable the unhandled handler.
|
3
7
|
|
4
8
|
## V0.1.2
|
@@ -18,7 +18,7 @@ module Slackify
|
|
18
18
|
|
19
19
|
def unhandled_handler=(handler)
|
20
20
|
raise Exceptions::InvalidHandler, "#{handler.class} is not a subclass of Slackify::Handlers::Base" unless
|
21
|
-
handler
|
21
|
+
handler < Handlers::Base
|
22
22
|
|
23
23
|
@unhandled_handler = handler
|
24
24
|
end
|