flipper-notifications 0.1.9 → 0.1.11

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 125ec86dec5bacf8e5da2931bb87f6a62bdef133e4a703f0132bc5d788bceac3
-  data.tar.gz: 90ec89c923006d4cd8fb3abc09e05f415bf04340f674d7ad0aa838987ae9b607
+  metadata.gz: b89e1c2fa5d254aebc89291bb50eec14b5687d9ea95f17f061e8f4972cc452f8
+  data.tar.gz: 870159e8ebf702200423b873448e8ac63140322fb4dbe6f811c746805ecdbf5b
 SHA512:
-  metadata.gz: edabeb8b4bc73721455f2504a47e8d89663a84af393d8e1d894bf1ad0cfa8c7a6eeb17ed40f2ee4b719aabcce0c66272090e4c540a152c985c989ce9cc77669e
-  data.tar.gz: 3a1bcc02e565fb5e7c821667b1d9f3c3119c6072e6fb5a7d6ba0822249c845fd9d0e37dada0cf93f7913440f68da7dea8ba21665cd71dd6493e3ae44e6600e87
+  metadata.gz: 63da6fdb0abb5067d5f1c6dd09e7103c1172fa3e294fb9e30817205ba75986c07c3f4aa9ba84328ac41790306e41d256657fdca09a7751a7135faad149d6ebf4
+  data.tar.gz: cf2ead088adc75c0aa2fb4c8c82b818264c89bd9bdd7d551a22dc16acb7808136b3a268f680e72b72069143d62172a0e3df5c3b7f5c3f4823c4263c9b2aba8df

data/.rubocop.yml

@@ -30,6 +30,9 @@ Metrics/CyclomaticComplexity:
 Metrics/MethodLength:
   Enabled: false
 
+Metrics/PerceivedComplexity:
+  Enabled: false
+
 Style/Documentation:
   Enabled: false
 

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    flipper-notifications (0.1.9)
+    flipper-notifications (0.1.11)
       activesupport (>= 7, < 8.2)
       flipper (>= 0.24, < 2.0)
       httparty (~> 0.17)
@@ -104,6 +104,7 @@ PLATFORMS
   arm64-darwin-21
   arm64-darwin-23
   arm64-darwin-24
+  arm64-darwin-25
   x86_64-linux
 
 DEPENDENCIES

data/README.md

@@ -53,6 +53,54 @@ Flipper::Notifications.configure do |config|
 end
 ```
 
+### Stale State with Cached Adapters
+
+Notifications are rendered inside a background job (`WebhookNotificationJob`),
+which may run in a **different process** from the one that changed the feature.
+The message ("The feature is now fully enabled/disabled", the list of groups,
+actors, and percentages) is built by reading the feature's current state at
+job-run time.
+
+If your Flipper adapter is fronted by a **per-process cache** — for example an
+in-memory `ActiveSupportCacheStore` layer — the process running the job can hold
+a stale value: enabling a feature in your web process does not invalidate a
+worker's in-memory cache. The notification then reports the wrong state.
+
+By default state is read through the global `Flipper`. Point `config.flipper` at
+a cache-free instance backed by your source of truth so notifications always
+render the real value:
+
+```ruby
+# config/initializers/flipper.rb
+
+Flipper::Notifications.configure do |config|
+  config.flipper = Flipper.new(Flipper::Adapters::ActiveRecord.new)
+end
+```
+
+This only affects how notifications **read** state; your application keeps using
+its cached `Flipper` everywhere else.
+
+### Slack invalid_blocks Errors
+
+Slack limits the size of webhook messages.  The Slack API returns a 400 status
+code in these cases with a message of `invalid_blocks`. If your feature is
+enabled for a lot of actors or a lot of groups, the length of the list of
+actor or group names can exceed Slack's limit.  To avoid these errors, you
+may configure a character limit sent in webhooks by configuring a
+`webhook_character_limit` in your initializer:
+
+```ruby
+# config/initializers/flipper.rb
+
+Flipper::Notifications.configure do |config|
+  config.webhook_character_limit = 3_000
+end
+```
+
+If you set this value, webhook messages will be shortened whenever they
+exceed the configured character limit.
+
 ### Implementing Your Own Webhooks
 
 This gem provides an implementation to send notifications to Slack via an

data/lib/flipper/notifications/configuration.rb

@@ -7,14 +7,32 @@ module Flipper
       def initialize
         @enabled   = false
         @notifiers = []
+        @webhook_character_limit = nil
+        @flipper = nil
       end
 
-      attr_accessor :enabled, :notifiers
+      attr_accessor :enabled, :notifiers, :webhook_character_limit
+      attr_writer :flipper
 
       def enabled?
         @enabled
       end
 
+      # The Flipper instance used to READ feature state when rendering a
+      # notification. Defaults to the global `Flipper`.
+      #
+      # Notifications are rendered in a background job, which may run in a
+      # different process from the one that changed the feature. If your Flipper
+      # adapter is fronted by a per-process cache (e.g. an in-memory
+      # ActiveSupportCacheStore), the reading process can hold a stale value and
+      # the message reports the wrong state. Point this at a cache-free instance
+      # backed by your source of truth to always render the real value, e.g.:
+      #
+      #   config.flipper = Flipper.new(Flipper::Adapters::ActiveRecord.new)
+      def flipper
+        @flipper || Flipper
+      end
+
     end
   end
 end

data/lib/flipper/notifications/feature_event.rb

@@ -20,7 +20,7 @@ module Flipper
       end
 
       def initialize(feature_name:, operation:)
-        @feature   = Flipper.feature(feature_name)
+        @feature   = Flipper::Notifications.configuration.flipper.feature(feature_name)
         @operation = operation.to_s
       end
 
@@ -40,7 +40,7 @@ module Flipper
       def feature_enabled_settings_markdown
         return "" unless feature.conditional?
 
-        [].tap do |settings|
+        markdown = [].tap do |settings|
           settings << "The feature is now enabled for:" if feature.conditional?
 
           settings << "- Groups: #{to_sentence(feature.enabled_groups.map(&:name).sort)}" if feature.enabled_groups.any?
@@ -53,6 +53,11 @@ module Flipper
 
           settings << "- #{feature.percentage_of_time_value}% of the time" if feature.percentage_of_time_value.positive?
         end.join("\n")
+
+        character_limit = Flipper::Notifications.configuration.webhook_character_limit
+        return markdown if character_limit.nil? || markdown.length <= character_limit
+
+        shortened_feature_enabled_settings_markdown[0...character_limit]
       end
 
       def noteworthy?
@@ -97,6 +102,21 @@ module Flipper
         end
       end
 
+      def shortened_feature_enabled_settings_markdown
+        [].tap do |settings|
+          settings << "The feature is now enabled for:" if feature.conditional?
+
+          settings << "#{feature.enabled_groups.size} Groups" if feature.enabled_groups.any?
+          settings << "#{feature.actors_value.size} Actors" if feature.actors_value.any?
+
+          if feature.percentage_of_actors_value.positive?
+            settings << "- #{feature.percentage_of_actors_value}% of actors"
+          end
+
+          settings << "- #{feature.percentage_of_time_value}% of the time" if feature.percentage_of_time_value.positive?
+        end.join("\n")
+      end
+
     end
   end
 end

data/lib/flipper/notifications/version.rb

@@ -2,6 +2,6 @@
 
 module Flipper
   module Notifications
-    VERSION = "0.1.9"
+    VERSION = "0.1.11"
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: flipper-notifications
 version: !ruby/object:Gem::Version
-  version: 0.1.9
+  version: 0.1.11
 platform: ruby
 authors:
 - Joel Lubrano
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2026-01-23 00:00:00.000000000 Z
+date: 2026-07-30 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activesupport
@@ -256,7 +256,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.5.9
+rubygems_version: 3.4.10
 signing_key:
 specification_version: 4
 summary: Rails-compatible Slack notifications for Flipper feature flags