trustid_sdk 0.2.0 → 0.2.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 301c57a0d10d984e3596a83163bac369d92daee4cc785a90553c0f6d958f3be7
-  data.tar.gz: 87e4f7fa237313d37ecc7b640239bebfe9353355e4e3f7e5cd338364637baf07
+  metadata.gz: 859be1d591ba0d789cde0a331e0f91d0aa31482cf65b6533485177b831ce57fd
+  data.tar.gz: '0987f36c03253670c9d1e71c2197a4cdae34db043888a7d40fe365e849996483'
 SHA512:
-  metadata.gz: '09df2387ca97b8753e74c36fe72fddd3cb929bd1e02114e89151cb278e68471157e03d506d72c7ec4b23329c9446f2045f84117067ee5c7f81f6c6de7b22de4b'
-  data.tar.gz: c493a5aea56b14f9d85dfd30b6f11e8026bc82f976e524824977263e42da19fc738e224fb1dd92ee352b9ba825f95a7fa9e2245ded1e003041a2895c2982285e
+  metadata.gz: 63681452a6f1c9aef4a3931b090527cba3445f016d901ef6e4985d1def9c69cadbc274e2601c656b4b5feeaff04ea3c609949cd0459238ca023704b4ca512938
+  data.tar.gz: 53306ffe7ae8eb2214c370689754e476e01972e0b4a9c8c827b2092e9c75ffb97b016e553c8025caa8c1c89e2951d8433693e7c4426f56eee00b82b974fc94f1

data/README.md

@@ -35,9 +35,9 @@ end
 
 ### Device ID
 
-`device_id` can be a string or a proc (or any object that responds to `call`). When it is a proc, it is invoked each time the SDK needs the device ID (e.g. for requests and reports), and the returned value is used.
+`device_id` can be a string or a proc (or any object that responds to `call`). When it is a proc, it is invoked **once when the client is created** (at login), and that value is used for the lifetime of the client. The device ID is then static for all requests made with that client.
 
-This is particularly useful for **parallel usage**: if you run multiple clients or workers, each needs a distinct device ID and session. If you reuse the same device ID, the next login for that device invalidates the previous session. Setting `device_id` to a proc that returns a new value per client (e.g. `-> { "prefix-#{SecureRandom.uuid}" }`) ensures each logical “device” gets a unique ID and its own session.
+This is particularly useful for **parallel usage**: if you run multiple clients or workers, each needs a distinct device ID and session. If you reuse the same device ID, the next login for that device invalidates the previous session. Setting `device_id` to a proc that returns a new value per client (e.g. `-> { "prefix-#{SecureRandom.uuid}" }`) ensures each client gets a unique ID and its own session, while keeping the same device ID for every request within that process.
 
 ```ruby
 require 'securerandom'

data/lib/trustid_sdk/client.rb

@@ -2,20 +2,16 @@
 
 module TrustID
   class Client
-    attr_reader :server_url
+    attr_reader :device_id, :server_url
     attr_accessor :session_id
 
     def initialize
       config = TrustID.config
-      @device_id = config.device_id
+      raw = config.device_id
+      @device_id = raw.respond_to?(:call) ? raw.call : raw
       @server_url = config.server_url
       TrustID.client = self
       Services::Authentication.new(config.username, config.password).login
     end
-
-    def device_id
-      value = @device_id
-      value.respond_to?(:call) ? value.call : value
-    end
   end
 end

data/lib/trustid_sdk/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module TrustID
-  VERSION = '0.2.0'
+  VERSION = '0.2.1'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: trustid_sdk
 version: !ruby/object:Gem::Version
-  version: 0.2.0
+  version: 0.2.1
 platform: ruby
 authors:
 - Tomislav Simnett