slack_line 1.2 → 1.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: bc23e7f575bc68df1c9824aacbde9b74050c14f82f765fc6929dc33ae909eccb
-  data.tar.gz: 45e54647313e4c71a27de6c8bda77826deaf7704ac8a5680c1439c5015f9b50e
+  metadata.gz: 4cd84ee81b09ef89c3f46abcd5c595c29f3ced087632368f343aded9e20ac731
+  data.tar.gz: b17c80d061d6c9a72ae68321079414213905baaed8d9f2b976a95d3c8fcbc4cc
 SHA512:
-  metadata.gz: 5c9d9e4c86c4ae41adac7a71a1044fe02aef53eaa823bc286862178b9fce6de8716d51a7833ed6ee118a550e29726358dd7b2a54df3bc78526074be65a125af4
-  data.tar.gz: fc217ed772fbbcbf1a27aa0911d24f2ef716c4b6ffed127f2c0959329b5358e510654a4d313c9d42e8a0168a7b88fe3c5d253d46545775175bd3671c3e593a65
+  metadata.gz: 1ff7cc5918a5b9395496814e1bbdb8494449ec202fd08ebd584afb1991d532cd9c62581e3c561d95acf2f308c5abea071c6b697a2754204103c15b8da81ef790
+  data.tar.gz: bfb562e958ec5d2b71a1d8bb1c895f2fd34b4e1a6c9cd5d557de4454f584cd77cc95db2e916ebc9e769b79128d62ea10e71da8a6de75a686e1cf93ef82674e4f

data/.github/workflows/rspec.yml

@@ -8,7 +8,7 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        ruby-version: ['3.2', '3.3', '3.4', 'head']
+        ruby-version: ['3.2', '3.3', '3.4', '4.0', 'head']
 
     steps:
       - uses: actions/checkout@v4

data/CHANGELOG.md

@@ -9,3 +9,24 @@ can do each of those things directly (for simpler messages).
 ## Version 1.1
 
 Fixed incorrect description/summary on gemspec.
+
+## Version 1.2
+
+Added disk-caching for the users and groups lists, through the `cache_path` and
+`cache_duration` config options and matching CLI flags. Added the
+`slack_line_stateful_thread` script, and `content` and `update` on `SentThread`.
+
+## Version 1.3
+
+`message` and `thread` now accept `to:`, as the README showed. Declared `reline`
+as a runtime dependency, which fixes a warning or `LoadError` under Bundler on
+Ruby 4.0. The invalid content error now lists the classes of the bad arguments.
+
+## Version 1.4
+
+**Breaking change:** calling `text` more than once in a `section` now raises an
+`ArgumentError`. It used to silently keep only the last text, because a Slack
+section block has one text field. Use one `section` per text.
+
+Fixed README examples that didn't run, including `context` inside a `section`,
+which Slack doesn't allow.

data/LICENSE

@@ -0,0 +1,20 @@
+Copyright 2026 Eric Mueller
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -13,13 +13,15 @@ sent_message = SlackLine.message("Something happened!", to: "#general").post
 
 # Construct a more complex message, then send it
 msg = SlackLine.message do
+  context "Don't worry! If this message surprises you, context @foobar"
+
+  # Like a Slack section block, a section holds one text and one link
   section do
-    context "Don't worry! If this message surprises you, context @foobar"
     text "A thing has happened"
-    text "Yeah, it happened for sure"
     link "How bad?", problems_path(problem.id)
   end
 
+  text "Yeah, it happened for sure"
   text "More details.."
 end
 sent_message = msg.post(to: "#general")
@@ -51,7 +53,7 @@ To update a SentThread, you'll need to choose  message:
 ```ruby
 sent_message.update "Edit: never mind, false alarm"
 sent_thread.first.update "Problem Resolved!"
-sent_thread.detect { |m| m =~ /Not yet safe/ }&.update do
+sent_thread.detect { |m| m.content.to_s.include?("Not yet safe") }&.update do
   text "it's safe now"
 end
 ```
@@ -82,7 +84,8 @@ be set via ENV or `SlackLine.configure`:
   is posted, and after each non-thread message is posted.
 * `cache_path` or `SLACK_LINE_CACHE_PATH` - a directory path for
   disk-caching the users and groups lists fetched from the Slack API.
-  When set, SlackLine will use the [lightly](https://github.com/DannyBen/lightly)
+  When set, SlackLine will use the
+  [lightly](https://github.com/DannyBen/lightly)
   gem to cache results to disk, which avoids redundant API calls across
   separate runs. Requires `lightly` to be installed as an optional
   dependency - if it is not available, a `DiskCaching::NoLightly` error
@@ -118,7 +121,7 @@ SlackLine methods dispatch to), but you can construct additional clients
 with their own configs easily:
 
 ```ruby
-Slackline.configure do |config|
+SlackLine.configure do |config|
   config.slack_token = ENV["TOKEN"]
   config.default_channel = "#general"
   config.bot_name = "FooBot"
@@ -127,7 +130,7 @@ end
 # Now SlackLine.message (et al) will use SlackLine.client,
 # configured as above.
 
-BAR_SLACK = SlackLine::Client.new(default_channel: "#team-bar", bot_name: "BarBot")
+BAR_SLACK = SlackLine::Client.new(SlackLine.configuration, default_channel: "#team-bar", bot_name: "BarBot")
 
 # And now you can call those methods on `BAR_SLACK` to use a different
 # default channel and name
@@ -138,11 +141,11 @@ BAR_SLACK.message("Message 3", to: "#bar-team-3").post
 
 ## CLI Scripts
 
-The gem ships with three executable scripts for sending and managing Slack messages
-from the command line. All three accept `-t`/`--slack-token TOKEN` and
+The gem ships with three executable scripts for sending and managing Slack
+messages from the command line. All three accept `-t`/`--slack-token TOKEN` and
 `-n`/`--bot-name NAME` to override the corresponding environment variables.
-Configuration can also come from `SLACK_LINE_SLACK_TOKEN` and friends as described
-above.
+Configuration can also come from `SLACK_LINE_SLACK_TOKEN` and friends as
+described above.
 
 ### `slack_line_message`
 
@@ -177,7 +180,8 @@ Options:
   required with `--update` on a thread)
 * `-s`/`--save PATH` - write the sent/updated result to PATH as JSON
 * `-u`/`--look-up-users` - resolve `@mentions` via the Slack API
-* `--cache-path PATH` / `--cache-duration DURATION` - disk-cache user/group lookups
+* `--cache-path PATH` / `--cache-duration DURATION` - disk-cache user/group
+  lookups
 * `--no-backoff` - disable per-message sleep delays
 
 When no content arguments are given and no DSL is piped, the script reads DSL
@@ -224,8 +228,9 @@ and appends replies along the way. The sent message is persisted to a file;
 subsequent invocations load and re-persist that file to know which Slack message
 to update.
 
-Messages are formatted as `[STATE] body`. The `--state` and `--message` flags each
-update their respective part independently; omitting one leaves it unchanged on update.
+Messages are formatted as `[STATE] body`. The `--state` and `--message` flags
+each update their respective part independently; omitting one leaves it
+unchanged on update.
 
 ```sh
 # Initial post - creates /tmp/deploy.json and posts "[running] Deploy started"
@@ -247,14 +252,16 @@ slack_line_stateful_thread --path /tmp/deploy.json --thread --message "Step 1 co
 
 Options:
 
-* `--path PATH` - (required) file path used to persist the sent message between invocations
-* `-p`/`--post-to TARGET` - channel or user; required on the first call, forbidden
-  thereafter
-* `-s`/`--state STATE` - the state label shown in brackets; required on first call
-* `-m`/`--message MESSAGE` - the message body; required on first call and when using
-  `--thread`
-* `--thread` - append a reply instead of updating the main message (mutually exclusive
-  with `--state`)
+* `--path PATH` - (required) file path used to persist the sent message between
+  invocations
+* `-p`/`--post-to TARGET` - channel or user; required on the first call,
+  forbidden thereafter
+* `-s`/`--state STATE` - the state label shown in brackets; required on first
+  call
+* `-m`/`--message MESSAGE` - the message body; required on first call and when
+  using `--thread`
+* `--thread` - append a reply instead of updating the main message (mutually
+  exclusive with `--state`)
 
 ## Slack App Permissions
 
@@ -262,9 +269,10 @@ In order to post/update messages, the app behind your `SLACK_LINE_TOKEN` can use
 these permissions:
 
 * `chat:write` - send messages at all.
-* `chat:write.public` - send messages to public channels your app _isn't a member
-  of_ (so you don't need to invite them to the relevant channels to make them work).
+* `chat:write.public` - send messages to public channels your app _isn't a
+  member of_ (so you don't need to invite them to the relevant channels to make
+  them work).
 * `im:write` - start direct messages with individuals.
-* `users:read` and `usergroups:read` - look up users/groups for (a) messaging them
-  directly or (b) supporting the `look_up_users` config option (for those more
-  restrictive workspaces)
+* `users:read` and `usergroups:read` - look up users/groups for (a) messaging
+  them directly or (b) supporting the `look_up_users` config option (for those
+  more restrictive workspaces)

data/lib/slack_line/client.rb

@@ -12,9 +12,9 @@ module SlackLine
 
     memoize def slack_client = Slack::Web::Client.new(token: configuration.slack_token)
 
-    def message(*text_or_blocks, &dsl_block) = Message.new(*text_or_blocks, client: self, &dsl_block)
+    def message(*text_or_blocks, to: nil, &dsl_block) = Message.new(*text_or_blocks, client: self, to:, &dsl_block)
 
-    def thread(*messages, &dsl_block) = Thread.new(*messages, client: self, &dsl_block)
+    def thread(*messages, to: nil, &dsl_block) = Thread.new(*messages, client: self, to:, &dsl_block)
 
     memoize def users = Users.new(client: self)
 

data/lib/slack_line/message.rb

@@ -3,14 +3,17 @@ module SlackLine
     extend Forwardable
     include Memoization
 
-    def initialize(*text_or_blocks, client:, &dsl_block)
+    def initialize(*text_or_blocks, client:, to: nil, &dsl_block)
       @text_or_blocks = text_or_blocks
       @dsl_block = dsl_block
       @client = client
+      @to = to
 
       validate!
     end
 
+    attr_reader :to
+
     memoize def content
       if @dsl_block
         MessageContext.new(&@dsl_block).content
@@ -30,7 +33,7 @@ module SlackLine
       "https://app.slack.com/block-kit-builder##{escaped_json}"
     end
 
-    def post(to: nil, thread_ts: nil) = MessageSender.new(message: self, client:, to:, thread_ts:).post
+    def post(to: nil, thread_ts: nil) = MessageSender.new(message: self, client:, to: to || self.to, thread_ts:).post
 
     private
 
@@ -49,7 +52,7 @@ module SlackLine
 
     def validate_type!
       unless @text_or_blocks.empty? || blocks?(@text_or_blocks) || strings?(@text_or_blocks)
-        raise(ArgumentError, "Invalid content type: #{@text_or_blocks.class}")
+        raise(ArgumentError, "Invalid content type: #{@text_or_blocks.map(&:class).uniq.join(", ")}")
       end
     end
 

data/lib/slack_line/section_context.rb

@@ -12,6 +12,8 @@ module SlackLine
     attr_reader :content
 
     def text(content, plain: false)
+      raise(ArgumentError, "A section can only have one text.") if @in_progress_section.text
+
       if plain
         @in_progress_section.plain_text(text: content)
       else

data/lib/slack_line/thread.rb

@@ -4,14 +4,17 @@ module SlackLine
     include Enumerable
     include Memoization
 
-    def initialize(*supplied_messages, client:, &dsl_block)
+    def initialize(*supplied_messages, client:, to: nil, &dsl_block)
       @supplied_messages = supplied_messages
       @dsl_block = dsl_block
       @client = client
+      @to = to
 
       validate!
     end
 
+    attr_reader :to
+
     # an Array of SlackLine::Messages
     memoize def messages = message_contents.map { |mc| convert_supplied_message(mc) }
 
@@ -20,11 +23,12 @@ module SlackLine
     memoize def builder_urls = messages.map(&:builder_url)
 
     def post(to: nil)
+      target = to || self.to || messages.filter_map(&:to).first
       sent_messages = []
       thread_ts = nil
 
       messages.each do |message|
-        sent = message.post(to:, thread_ts:)
+        sent = message.post(to: target, thread_ts:)
         thread_ts ||= sent.ts
         sent_messages << sent
       end

data/lib/slack_line/version.rb

@@ -1,3 +1,3 @@
 module SlackLine
-  VERSION = "1.2".freeze
+  VERSION = "1.4".freeze
 end

data/slack_line.gemspec

@@ -46,4 +46,5 @@ Gem::Specification.new do |spec|
 
   spec.add_dependency "slack-ruby-block-kit", "~> 0.23.0"
   spec.add_dependency "slack-ruby-client", "~> 3.1.0"
+  spec.add_dependency "reline", ">= 0.6"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: slack_line
 version: !ruby/object:Gem::Version
-  version: '1.2'
+  version: '1.4'
 platform: ruby
 authors:
 - Eric Mueller
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2026-03-16 00:00:00.000000000 Z
+date: 2026-11-05 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rspec
@@ -164,6 +164,20 @@ dependencies:
     - - "~>"
       - !ruby/object:Gem::Version
         version: 3.1.0
+- !ruby/object:Gem::Dependency
+  name: reline
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0.6'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0.6'
 description: |
   Sending messages with the Slack API is not that difficult, but I've had
   to solve the same problems a lot of times at different companies. This
@@ -189,6 +203,7 @@ files:
 - ".standard.yml"
 - CHANGELOG.md
 - Gemfile
+- LICENSE
 - README.md
 - bin/slack_line_message
 - bin/slack_line_stateful_thread