Releases: jusleg/slackify
v0.4.2
v0.4.1
v0.4.0
V0.4.0
- BREAKING CHANGE: Use
approved_bot_idsinstead ofwhitelisted_bot_ids(6243c11) by @DougEdey - Add support for named parameters in commands (PR #12) by @DougEdey
- Add support for custom parameters in commands (PR #17) by @DougEdey
- Tidy up some tests
- Update to Slack-Ruby-Client 0.15.1 for pagination support
0.3.2
0.3.0
- Add code documentation and improve exception message
- Add whitelisting of bot ids in the configuration through
whitelisted_bot_ids= - Refactored Handler configuration into
Slackify::RouterandSlackify::Handlers::Factory - Improved testing
- Remove the need to perform
Slackify.load_handler - Breaking change: Given that we now load the handlers on
Slack.configure, the configuration step done inconfig/application.rbwill have to be done in an initializer to have all the handler class loaded.
0.2.0
Update custom_event_subtype_handlers to custom_message_subtype_handlers and add support for custom_event_type_handlers. This is a breaking change since we rename the field that was previously used. To fix, update any calls from custom_event_subtype_handlers to custom_message_subtype_handlers and you should be good to go.
0.1.5
Update how the bot_id is set in the handler configuration. You can disable the slack auth test (which is used to obtain the bot_id) by setting SLACK_AUTH_SKIP=1 in your environment variables. If you are running in a Rails environment other than production, development or staging and would like to use the bot for real requests, you can trigger a manual auth test by calling Slackify.configuration.handlers.bot_auth_test. Gemfile.lock was removed.
0.1.4
0.1.3
0.1.2
- Renaming the gem from toddlerbot to slackify.
- Cleanup of
lib/slackifyfolder. - Added a new configuration: unhandled_handler. You can specify a subclass of
Slackify::Handlers::Basein the config. This class will be called with#unhandledwhen a message has no regex match.