A collection of ruby objects that represent Slack's block kit.
You can play around with the block kit using Slack's block kit builder!
The 'blocks' availables are split in line with how Slack documents them, that is:
Slack::BlockKit::Layout
contains the Layout blocksSlack::BlockKit::Element
contains the Block elementsSlack::BlockKit::Composition
contains the Message composition objects
Add this line to your application's Gemfile:
gem 'slack-ruby-block-kit'
And then execute:
$ bundle
Or install it yourself as:
$ gem install slack-ruby-block-kit
Finally, require this:
require 'slack-ruby-block-kit'
Here are a few examples that might help you get started!
require 'faraday'
require 'slack-ruby-block-kit'
require 'json'
a_prebuilt_block = Slack::BlockKit::Layout::Section.new
text = Slack::BlockKit::Composition::Mrkdwn.new(text: ':wave: *hello*')
an_image = Slack::BlockKit::Element::Image.new(image_url: 'https://git.io/fjDW8', alt_text: 'a picture')
a_prebuilt_block.accessorise(an_image)
a_prebuilt_block.text = text
blocks = Slack::BlockKit.blocks do |b|
b.section do |s|
s.plain_text(text: 'Some plain text message!')
s.button(text: 'A button that is important', style: 'primary', action_id: 'id')
end
b.divider
b.context do |c|
c.mrkdwn(text: '_some italicised text for context_')
end
b.append(a_prebuilt_block)
end
webhook_url = 'https://hooks.slack.com/services/your/webhook/url'
body = { blocks: blocks.as_json, text: 'New block message!' }
response = Faraday.post(
webhook_url,
body.to_json,
'Content-Type' => 'application/json'
)
This will create a message like this:
You can also check out the slackerduty
project for some example,
Slackerduty::Alert
and Slackerduty::Blocks
may be helpful places to start.
Bug reports and pull requests are welcome on GitHub at https://github.com/CGA1123/slack-ruby-block-kit
See issues if you want any inspiration as to what to help with!
The gem is available as open source under the terms of the MIT License.
Releasing is automated via the .github/workflows/release.yml
which allows for
an OTP code to be passed in to authorize the release with MFA. If GitHub
Actions is running slow it might take another attempt to make sure the OTP code
is still valid when the workflow tries to push.
- Update
CHANGELOG
for the latest version (remember to update the comparison links + add in anUnreleased
section again) - Update
lib/slack/block_kit/version.rb
and runbundle
to update theGemfile.lock
- Push that!
- Run the
Release
workflow