slack-ruby / slack-ruby/slack-ruby-client

BlockKit Helper

Open
#316 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

new feature question
Dominant language
Ruby
Stars
1.3k
Forks
222
Avg merge
1d 14h
Merged PRs (30d)
3

Description

Hello, I've spent a few hours putting together what I think is a fairly good prototype for composing BlockKit-based messages in Ruby. Currently, it has what I personally need from it for my own project, and no tests or meaningful docs. That's adequate for my personal project, but not for contributing to something bigger.

I'd like to gauge how much interest there would be in integrating my stuff into slack-ruby-client. (Alternatively, I could look into releasing it as a separate gem that can merely plug into slack-ruby-client.) From that, I figure I could decide how much work to put in to finish fleshing out all the other classes and writing an adequate test suite and documentation for the whole thing.

Current progress is over here: https://github.com/slack-ruby/slack-ruby-client/compare/master...saraid:saraid/slack-blockkit-helper

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the linked comparison from master to understand the BlockKit helper prototype and its current scope. The issue mentions no specific files or tests; determine whether the work belongs in slack-ruby-client or a separate gem, then define the remaining classes, test coverage, and documentation needed for a complete contribution.

Written by the indexing model from the issue text.

Assessment

Tech stack
ruby
Domain
api
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.