ruby-clock 2.0.0.beta4 → 2.0.0.beta5

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 8900519602f68a1eb7e0a5b49aa1752c5a42ffb65a16b409b8f12c003237c568
-  data.tar.gz: bb9d30d35bafa38b970f061faa0416bffb66197f5fddd5d46a691c05e04fe82b
+  metadata.gz: 4030e34d3273a3b96cabaa879b0d52965ff35e9ad13afebcb8932b9244512836
+  data.tar.gz: dd6b624f190797e3daa9e1481ed27e1347d56df0df4a76a7e3855890eff51ef1
 SHA512:
-  metadata.gz: 50482fd2178c9098bd8e2eb1218f56c56596d5983d82571246d5516cd977227a344598f056019027f2b97222ffc8a628eed503ed2d10defea116bfe5d6b953f1
-  data.tar.gz: 5eb78d5f6dffb1d09d09e9d1ada59a0bae9646253f789affec38311237b74b937192b1f7a414b2a5ff3e8fc2b34a3beb6fe1e8fda8a6aeffedfac80941e8a5a5
+  metadata.gz: 052a4b986dc7ad4665b446ec5adb2c371aaddc4e503696b6127a977357ea2c3d6c9cd3e3a28b4cca4c8e90cfc0c3cae5c311d55c16f8d7ba11c0d130f7b2c4a2
+  data.tar.gz: 43eab7d34b9259380a9c5939fbca53d98cf17dcaa89ab10f9d57343f64fea9dccdd495554d144fef3929f48d561eb327d652e170476be184ea80de96c8d06bf1

data/CHANGELOG.md

@@ -24,8 +24,7 @@
 * The top of every Clockfile must begin with `using RubyClock::DSL`
 * rake and shell runners must be invoked like so: `RubyClock::Runners.rake`, `RubyClock::Runners.shell`, etc.
 * If you have an existing `def schedule.around_trigger`, you will need to change it to use the new
-  `around_action` method. Failure to change this will silently appear to keep working,
-  but will break the rails reloader/executor implementation.
+  `around_action` method.
 * Your existing Clockfile will still work, but you now have the option to use
   `every`, `cron`, and `on_error` at the top-level, without referencing `schedule`.
   See the readme for examples.

data/example-app/Clockfile

@@ -52,3 +52,7 @@ every('2 seconds') do
     puts "💥 we do not expect runners to be available inside a job, but it is"
   end
 end
+
+# def schedule.around_trigger(job_info, &job_proc)
+#   puts "ruby-clock 1-style around trigger!"
+# end

data/example-app/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: ..
   specs:
-    ruby-clock (2.0.0.beta4)
+    ruby-clock (2.0.0.beta5)
       method_source
       rufus-scheduler (~> 3.8)
 

data/exe/clock

@@ -18,5 +18,6 @@ rescue => clockfile_error
   raise
 end
 
+RubyClock.instance.ensure_around_trigger_has_not_been_redefined
 RubyClock.instance.freeze_around_actions
 RubyClock.instance.run_jobs

data/lib/ruby-clock/around_actions.rb

@@ -15,6 +15,19 @@ module RubyClock::AroundActions
         job_info
       )
     end
+
+    self.around_trigger_code_location = schedule.method(:around_trigger).source_location
+  end
+
+  def ensure_around_trigger_has_not_been_redefined
+    if around_trigger_code_location != schedule.method(:around_trigger).source_location
+      raise <<~MESSAGE
+
+        You need to change your around_trigger definition to use around_actions instead.
+
+        It's easy and fun! https://github.com/jjb/ruby-clock/blob/main/CHANGELOG.md#migrating-from-ruby-clock-version-1-to-version-2
+      MESSAGE
+    end
   end
 
   def call_with_around_action_stack(wrappers, job_proc, job_info)

data/lib/ruby-clock/version.rb

@@ -1,3 +1,3 @@
 class RubyClock
-  VERSION = "2.0.0.beta4"
+  VERSION = "2.0.0.beta5"
 end

data/lib/ruby-clock.rb

@@ -17,7 +17,7 @@ class RubyClock
   include RubyClock::Shell
   include RubyClock::AroundActions
 
-  attr_accessor :on_error
+  attr_accessor :on_error, :around_trigger_code_location
 
   def initialize
     set_up_around_actions

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: ruby-clock
 version: !ruby/object:Gem::Version
-  version: 2.0.0.beta4
+  version: 2.0.0.beta5
 platform: ruby
 authors:
 - John Bachir