tramway 2.3.1.1 → 2.3.1.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 0f94931c225d093e9cb11e8957ae333b66a2a6feb0e36427c77bbe864ae75433
-  data.tar.gz: a16912c9f8ea5da24eabbba7dd0f0524f1ef0f057c14a6af6f56c2d930b08b37
+  metadata.gz: afb266e8ff0e57296500fc2181b623ef4abffbe184be90bbb3a6a61431cfcbc8
+  data.tar.gz: 7e23e932ff24c6f5c93bbc3a3cd2365c2f66e7b121a690f9c56e51cfe5c3ac60
 SHA512:
-  metadata.gz: 0174d5e8d6ed3f337bcbc01523471d651d333d30104399da24d0e9ac16dd0a7549982e3ad77b8ff15c8af26c59791e11120c4afee462215870bbf4c1a9fbdf81
-  data.tar.gz: 9e229945662dadadb01ca4075bf0a2da71b90fdca30e4b687144424d72e9929face26facbc94cee1c6e01cdda29c8c72a4ef072d0784fb46329bfc3c6ed257c2
+  metadata.gz: 48eca5f7a2a9c24681f73f164b997e59b21e75efd761fd99f8f765752ed16b226d8823ee124c60fca08c2944c49b91b38d2e8b4808faf424fc804dfb0b8aec40
+  data.tar.gz: 11835fac94f5d47052e64a8a6de159eb53385b1ee9dc78f1a0500c8a7b4329eb1f0f607ff8e84c078a66becd1387f0403d78f3b9fe6e43dd6c905ab695c3b50b

data/README.md

@@ -863,6 +863,9 @@ the Tailwind color family explicitly.
 that receives new messages. Each message must include an `:id` and a `:type` (either `:sent` or `:received`). Additional
 message fields like `text`, `data`, or `sent_at` are forwarded to `tramway/chats/message_component`.
 
+Use `send_messages_enabled:` to control whether users can send new messages from the rendered form. It defaults to `true`.
+When set to `false`, the text field is disabled and the waiting placeholder is shown.
+
 ```haml
 -# Haml example
 - messages = [
@@ -872,7 +875,8 @@ message fields like `text`, `data`, or `sent_at` are forwarded to `tramway/chats
 = tramway_chat chat_id: 'support-chat',
   messages: messages,
   message_form: @message_form,
-  send_message_path: chat_messages_path
+  send_message_path: chat_messages_path,
+  send_messages_enabled: @chat.open?
 ```
 
 ```erb
@@ -881,7 +885,8 @@ message fields like `text`, `data`, or `sent_at` are forwarded to `tramway/chats
 <%= tramway_chat chat_id: 'support-chat',
   messages: messages,
   message_form: @message_form,
-  send_message_path: chat_messages_path %>
+  send_message_path: chat_messages_path,
+  send_messages_enabled: @chat.open? %>
 ```
 
 

data/app/components/tramway/chats/message_component.html.haml

@@ -16,11 +16,11 @@
 
     - if pending?
       .pb-1
-        = inline_svg 'icons/spinner.svg', class: 'w-4 h-4 text-white animate-spin'
+        -# = inline_svg 'icons/spinner.svg', class: 'w-4 h-4 text-white animate-spin'
 
     - if failed?
       .pb-1
-        = inline_svg 'icons/cross.svg', class: 'w-6 h-6 text-red-200'
+        -# = inline_svg 'icons/cross.svg', class: 'w-6 h-6 text-red-200'
 
     - if data_view == :table
       = component 'tramway/chats/messages/table', data:

data/docs/AGENTS.md

@@ -131,6 +131,8 @@ Inherit all components from Tramway::BaseComponent
 When you need chat UI, use the `tramway_chat` helper. Pass `chat_id`, `messages`, `message_form`, and `send_message_path`.
 Each message must include `:id` and a `:type` of `:sent` or `:received`, and other keys (like `:text`, `:data`, `:sent_at`)
 are forwarded to `tramway/chats/message_component`. Use `message_form: nil` when you only need read-only chat rendering.
+Use `send_messages_enabled:` (defaults to `true`) to control whether the message input is enabled. Set it to `false`
+when chat should be visible but sending is temporarily unavailable.
 
 For live updates to a rendered `tramway_chat`, use `tramway_chat_append_message(chat_id:, message_type:, text:, sent_at:)`.
 This method is included in all controllers and ActiveRecord models. `message_type` must be `:sent` or `:received`, otherwise

data/lib/tramway/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Tramway
-  VERSION = '2.3.1.1'
+  VERSION = '2.3.1.2'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: tramway
 version: !ruby/object:Gem::Version
-  version: 2.3.1.1
+  version: 2.3.1.2
 platform: ruby
 authors:
 - kalashnikovisme