dexiecable 0.1.7 → 0.1.9

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 85944f789c9d0a2a10d718fbab783e4c9b89e00bb2ad0fe2cb5804648660447c
-  data.tar.gz: a17bc5ccd07702c90ea508b9261391980fbfa68e4bf1a5d1b9dc4f85f6a8c417
+  metadata.gz: 390eddcb71f97e5e8755696c49a8ce2417e7f8636e0e43be8742acd4f31f4b59
+  data.tar.gz: 2058ae8d76759483bc047b4e74622154335eb55fa2124052f518f51d14539a0d
 SHA512:
-  metadata.gz: 62b8fbad4ae8392ec0da800697247833a62cdd1dd8165f95ed05c6b81e4b97a4984e75eb3179481139e9bf8f2378641eecb50e2e7ba5503c94f445a9e30e7128
-  data.tar.gz: 17330cb1f871afb2b9599596e2d8f1cd882fe323c686f9464490b779e1f2fdfbb4c9b6a9bacca0bd2eb5751ff4001a93cea4f0cbb9dbacae4ab1a1d6489ac2a0
+  metadata.gz: 9057f8f5bdbb694a2673c47773db75d2d99a0f3383043908b51152f3f6279a4aabae9f4436dffeebd31e6882d684ca9f505f7a30e5bf1942de89787199a07589
+  data.tar.gz: 39b6503f4ac13bf8abbaae9352ea6b2355bf34f3210dfd2cd99d87413a39a606f389f39236cafca0143aa94621f8bb0be5835fb34c08027cca0d0c2a7ac6feac

data/README.md

@@ -1,6 +1,7 @@
 # DexieCable
 
-Run [Dexie.js](https://dexie.org) IndexedDB operations from your Rails ActionCable channels.
+> [!NOTE]
+> DexieCable is NOT a local-first solution, because it lacks the capability to automatically sync updates back to the server (this might be added later). For now, think of it as a real-time local-cache solution. Also, check out this [blog post introducing DexieCable](https://dev.to/buhrmi/real-time-rails-without-turbo-modern-reactive-uis-with-inertia-and-dexiecable-4lge).
 
 DexieCable augments ActionCable channels with a query DSL that mirrors the Dexie.js API, letting you push database mutations from the server to the client in real time. It also gives you a [`syncs_to_dexie`](#syncs_to_dexie--automatic-model-syncing) ActiveRecord macro for automatic change syncing.
 
@@ -33,7 +34,7 @@ An even more convenient way is to use the `syncs_to_dexie` macro (more info [bel
 
 ```ruby
 class Notification < ApplicationRecord
-  syncs_to_dexie via: UserChannel, to: :user
+  syncs_to_dexie via: -> { UserChannel[user] }
 end
 ```
 
@@ -57,19 +58,26 @@ npm install dexiecable
 yarn add dexiecable
 ```
 
-Configure it with your Dexie database and ActionCable consumer before subscribing:
+Pass your Dexie database as the first argument to `subscribe()`:
 
 ```js
-import { configure, subscribe } from "dexiecable";
+import { subscribe } from "dexiecable";
 import { db } from "./db";
-import { createConsumer } from "@rails/actioncable";
 
-configure({ db, consumer: createConsumer() });
-
-const sub = subscribe("UserChannel", { last_update: Date.now() });
+subscribe(db, "UserChannel");
 ```
 
-If you omit `consumer`, one is created for you automatically.
+A consumer is lazily created on the first `subscribe()` call. If you need to access or set the consumer explicitly, use `getConsumer()` and `setConsumer()`:
+
+```js
+import { getConsumer, setConsumer, createConsumer } from "dexiecable";
+
+// Get the consumer (creates one lazily if needed)
+const consumer = getConsumer();
+
+// Or set a custom one
+setConsumer(createConsumer("wss://example.com/cable"));
+```
 
 ## Usage
 
@@ -125,7 +133,15 @@ The full query chain is serialized as JSON and sent over ActionCable. The JS cli
 
 ### `syncs_to_dexie` — automatic model syncing
 
-Add to any ActiveRecord model. Just provide the channel class and the broadcast target.
+Add to any ActiveRecord model. The simplest approach: pass a Proc to `via` that returns a scoped channel.
+
+```ruby
+class Message < ApplicationRecord
+  syncs_to_dexie via: -> { UserChannel[current_user] }
+end
+```
+
+You can also pass a channel class with `to:` to have DexieCable handle the scoping:
 
 ```ruby
 class Message < ApplicationRecord
@@ -145,18 +161,19 @@ Internally, `syncs_to_dexie` sets up the following ActiveRecord callbacks:
 
 | Event | Action |
 |---|---|
-| `after_commit on: :create` | `channel.table(table).add(record.as_json_for_dexie)` |
-| `after_commit on: :update` | `channel.table(table).put(record.as_json_for_dexie)` |
-| `after_commit on: :destroy` | `channel.table(table).delete(record.id)` |
+| `after_commit on: :create` | `channel.table(table).add(as_json_for_dexie)` |
+| `after_commit on: :update` | `channel.table(table).update(id, as_json_for_dexie.slice(*saved_changes.keys))` |
+| `after_commit on: :destroy` | `channel.table(table).delete(id)` |
 
 #### Options
 
 | Option | Default | Description |
 |---|---|---|
-| `via:` | *(required)* | A DexieCable channel class |
-| `to:` | *(none)* | The stream target passed to `broadcast_to`. Symbol → calls `send`. String → used as-is. Proc → evaluated in record context. Returns a single recipient or collection. |
+| `via:` | *(required)* | A DexieCable channel class, or a Proc that returns a channel or scoped channel (e.g. `-> { UserChannel[current_user] }`) |
+| `to:` | *(none)* | The stream target passed to `broadcast_to`. Symbol → calls `send`. String → used as-is. Proc → evaluated in record context. Returns a single recipient or collection. Only used when `via` is a channel class. |
 | `table:` | model's `table_name` | Override the Dexie table name. A Proc is evaluated in the record's context. |
 | `only:` | `[:create, :update, :destroy]` | Limit which events trigger a sync |
+| `with:` | `:as_json_for_dexie` | Method name (Symbol) or Proc for serializing records |
 | `if:` | *(none)* | Symbol (method name) or Proc — only sync when it returns truthy |
 | `unless:` | *(none)* | Symbol (method name) or Proc — skip sync when it returns truthy |
 
@@ -164,25 +181,36 @@ You can combine multiple `syncs_to_dexie` declarations, each with different cond
 
 ```ruby
 class Message < ApplicationRecord
-  syncs_to_dexie via: UserChannel, to: -> { sender },
+  syncs_to_dexie via: -> { UserChannel[current_user] }
+  syncs_to_dexie via: -> { BoardChannel[board] },
                  if: :published?
-
-  syncs_to_dexie via: AdminChannel,
-                 unless: -> { draft? }
 end
 ```
 
 #### Customizing the synced payload
 
-Override `as_json_for_dexie` in your model:
+Override `as_json_for_dexie` in your model, or use the `with` option to specify a different method or Proc:
 
 ```ruby
 class Message < ApplicationRecord
-  syncs_to_dexie via: UserChannel, to: :sender
+  # Using the default as_json_for_dexie override:
+  syncs_to_dexie via: -> { UserChannel[current_user] }
 
   def as_json_for_dexie
     super.merge(room_name: room.name)
   end
+
+  # Or use a custom serializer method:
+  syncs_to_dexie via: AdminChannel,
+                 with: :admin_payload
+
+  def admin_payload
+    attributes.slice("id", "body", "flagged")
+  end
+
+  # Or a Proc:
+  syncs_to_dexie via: PublicChannel,
+                 with: -> { { id: id, summary: body.truncate(100) } }
 end
 ```
 
@@ -223,6 +251,60 @@ The JS side replays it as:
 dexie.messages.where("room_id").equals(5).add({ id: 1, text: "hello" })
 ```
 
+## Recipies
+
+### Use sequence IDs to avoid data loss
+
+A common pattern to avoid data loss during transient disconnections is using sequence IDs to bridge the offline gap. When a connection drops, updates continue on the server. Sending the client’s latest known sequence ID upon reconnect allows the backend to query and stream only the records missed while offline.
+
+To enable this, DexieCable ships its own version of the ActionCable client with one key
+extension: **channel params can be functions**. When a param value is a
+function, it is called and awaited at subscribe time — use this to submit the latest known sequence ID on connection:
+
+```js
+import { subscribe } from "dexiecable";
+import { db, getLastSeqId } from './database';
+
+const roomId = 123;
+
+subscribe(db, {
+  channel: "RoomChannel",
+  room_id: roomId,
+  seq_id: () => getLastSeqId(roomId) // evaluated fresh on each reconnect
+});
+```
+
+Send missed messages on reconnection:
+
+```ruby
+class RoomChannel < ApplicationChannel:Base
+  def subscribed
+    stream_from "room:#{params[:room_id]}"
+    missed_messages = room.messages.where("seq_id > ?", params[:seq_id])
+    table("messages").bulkAdd(missed_messages)
+  end
+end
+```
+
+You might want to have look at the [Sequenced](https://github.com/derrickreimer/sequenced) gem to automatically add sequence IDs to your records.
+
+### Multi-user environments
+
+In multi-user or multi-tenant applications, you can isolate records by binding different subscription channels to separate Dexie database instances. This prevents local data leaks between user accounts and keeps private user data separate from public or shared feeds.
+
+```js
+
+import Dexie from 'dexie'
+import { subscribe } from 'dexiecable'
+
+const userDB = new Dexie("user_"+userId)
+const sharedDB = new Dexie("shared")
+
+subscribe(userDB, 'UserChannel')
+subscribe(sharedDB, 'PublicChannel')
+
+```
+
 ## License
 
 MIT

data/lib/dexiecable/active_record_ext.rb

@@ -9,17 +9,19 @@ module DexieCable
       # DexieCable channel.
       #
       #   class Message < ApplicationRecord
-      #     syncs_to_dexie via: UserChannel, to: :sender
-      #     syncs_to_dexie via: UserChannel, to: "global_feed"
-      #     syncs_to_dexie via: UserChannel, to: -> { conversation.users }
+      #     syncs_to_dexie via: -> { UserChannel[current_user] }
       #     syncs_to_dexie via: PublicChannel
+      #     syncs_to_dexie via: UserChannel, to: :user
+      #     syncs_to_dexie via: UserChannel, to: -> { conversation.users }
+      #     syncs_to_dexie via: -> { tenant_channel }
       #   end
       #
-      # @param via     [Class] A DexieCable channel class. When +to+
+      # @param via     [Class, Proc] A DexieCable channel class, or a Proc
+      #                  evaluated in record context that returns a channel
+      #                  class or a scoped channel (e.g.
+      #                  +-> { UserChannel[current_user] }+). When +to+
       #                  is given, each recipient is mapped through
       #                  +via[to]+ to produce scoped channels.
-      #                  Without +to+, +via+ is used directly as an
-      #                  unscoped channel.
       # @param to      [Proc, Symbol, String] A Proc evaluated in record
       #                  context, a Symbol to call via +send+, or a String
       #                  used directly as the stream name for +broadcast_to+.
@@ -30,16 +32,19 @@ module DexieCable
       #                 evaluated in the record's context.
       # @param only    [Array<Symbol>] Limit which lifecycle events sync.
       #                 Default: [:create, :update, :destroy].
+      # @param with [Symbol, Proc] Method name or proc to use for
+      #                 serializing records (defaults to :as_json_for_dexie).
       # @param if      [Symbol, Proc] Only sync if the given method or proc
       #                 returns truthy (evaluated in the record's context).
       # @param unless  [Symbol, Proc] Skip sync if the given method or proc
       #                 returns truthy (evaluated in the record's context).
-      def syncs_to_dexie(via:, to: nil, table: nil, only: nil, **options)
+      def syncs_to_dexie(via:, to: nil, table: nil, only: nil, with: nil, **options)
         events     = Array(only || %i[create update destroy])
         conditions = options.slice(:if, :unless)
+        serializer = with || :as_json_for_dexie
 
         @dexie_sync_configs ||= []
-        @dexie_sync_configs << { via: via, to: to, table: table, only: events, **conditions }
+        @dexie_sync_configs << { via: via, to: to, table: table, only: events, with: serializer, **conditions }
 
         if events.include?(:destroy)
           before_destroy :dexie_sync_before_destroy
@@ -56,7 +61,7 @@ module DexieCable
           after_commit on: :create, **conditions do
             Array(resolve_channel(via, to)).each do |channel|
               next unless channel
-              channel.table(resolve_table(table)).add(as_json_for_dexie)
+              channel.table(resolve_table(table)).add(serialize_record(serializer))
             end
           end
         end
@@ -66,7 +71,7 @@ module DexieCable
             Array(resolve_channel(via, to)).each do |channel|
               next unless channel
 
-              changes = as_json_for_dexie.slice(*saved_changes.keys)
+              changes = serialize_record(serializer).slice(*saved_changes.keys)
               channel.table(resolve_table(table)).update(id, changes)
             end
           end
@@ -77,11 +82,12 @@ module DexieCable
     private
 
     def resolve_channel(via, to = nil)
+      channel = via.is_a?(Proc) ? instance_exec(&via) : via
       if to
         recipients = resolve_recipient(to)
-        Array(recipients).map { |r| via[r] }
+        Array(recipients).map { |r| channel[r] }
       else
-        via
+        channel
       end
     end
 
@@ -101,6 +107,14 @@ module DexieCable
       end
     end
 
+    def serialize_record(serializer)
+      case serializer
+      when Proc   then instance_exec(&serializer)
+      when Symbol then send(serializer)
+      else serializer
+      end
+    end
+
     # Override in your model to customise the payload synced to Dexie.
     def as_json_for_dexie
       as_json

data/lib/dexiecable/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module DexieCable
-  VERSION = "0.1.7"
+  VERSION = "0.1.9"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: dexiecable
 version: !ruby/object:Gem::Version
-  version: 0.1.7
+  version: 0.1.9
 platform: ruby
 authors:
 - Stefan Buhrmester