From 0e631a314a5f64f714c74a8e9805d1cdb2a29bed Mon Sep 17 00:00:00 2001 From: Jack Weeden Date: Fri, 21 Feb 2025 11:39:12 +0000 Subject: [PATCH] Update RemoteSynchronizable documentation This concern was reverted in d045d1d to the previous implementation where the client is explicitly set as a class variable rather than by a method call, but it looks like the documentation still reflects the previous way. Similarly, it no longer uses lifecycle callbacks but relies on these methods to be explicitly called. --- app/models/concerns/remote_synchronizable.rb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/app/models/concerns/remote_synchronizable.rb b/app/models/concerns/remote_synchronizable.rb index 8c2fc684..3c1209a8 100644 --- a/app/models/concerns/remote_synchronizable.rb +++ b/app/models/concerns/remote_synchronizable.rb @@ -1,11 +1,11 @@ -# Enhances a model with lifecycle callbacks to synchronise it with a remote resource using a client +# Enhances a model with methods to synchronise it with a remote resource using a client # class (conventionally located in `app/clients/`). # # Example: # ```ruby # class Foo < ApplicationRecord # include RemoteSynchronizable -# remote_synchronize with: BarApi::FooClient +# self.remote_synchronizable_client_class = BarApi::FooClient # end # ``` #