ruby-clock 2.0.0.beta4 → 2.0.0.beta5
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/CHANGELOG.md +1 -2
- data/example-app/Clockfile +4 -0
- data/example-app/Gemfile.lock +1 -1
- data/exe/clock +1 -0
- data/lib/ruby-clock/around_actions.rb +13 -0
- data/lib/ruby-clock/version.rb +1 -1
- data/lib/ruby-clock.rb +1 -1
- metadata +1 -1
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA256:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 4030e34d3273a3b96cabaa879b0d52965ff35e9ad13afebcb8932b9244512836
|
4
|
+
data.tar.gz: dd6b624f190797e3daa9e1481ed27e1347d56df0df4a76a7e3855890eff51ef1
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 052a4b986dc7ad4665b446ec5adb2c371aaddc4e503696b6127a977357ea2c3d6c9cd3e3a28b4cca4c8e90cfc0c3cae5c311d55c16f8d7ba11c0d130f7b2c4a2
|
7
|
+
data.tar.gz: 43eab7d34b9259380a9c5939fbca53d98cf17dcaa89ab10f9d57343f64fea9dccdd495554d144fef3929f48d561eb327d652e170476be184ea80de96c8d06bf1
|
data/CHANGELOG.md
CHANGED
@@ -24,8 +24,7 @@
|
|
24
24
|
* The top of every Clockfile must begin with `using RubyClock::DSL`
|
25
25
|
* rake and shell runners must be invoked like so: `RubyClock::Runners.rake`, `RubyClock::Runners.shell`, etc.
|
26
26
|
* If you have an existing `def schedule.around_trigger`, you will need to change it to use the new
|
27
|
-
`around_action` method.
|
28
|
-
but will break the rails reloader/executor implementation.
|
27
|
+
`around_action` method.
|
29
28
|
* Your existing Clockfile will still work, but you now have the option to use
|
30
29
|
`every`, `cron`, and `on_error` at the top-level, without referencing `schedule`.
|
31
30
|
See the readme for examples.
|
data/example-app/Clockfile
CHANGED
data/example-app/Gemfile.lock
CHANGED
data/exe/clock
CHANGED
@@ -15,6 +15,19 @@ module RubyClock::AroundActions
|
|
15
15
|
job_info
|
16
16
|
)
|
17
17
|
end
|
18
|
+
|
19
|
+
self.around_trigger_code_location = schedule.method(:around_trigger).source_location
|
20
|
+
end
|
21
|
+
|
22
|
+
def ensure_around_trigger_has_not_been_redefined
|
23
|
+
if around_trigger_code_location != schedule.method(:around_trigger).source_location
|
24
|
+
raise <<~MESSAGE
|
25
|
+
|
26
|
+
You need to change your around_trigger definition to use around_actions instead.
|
27
|
+
|
28
|
+
It's easy and fun! https://github.com/jjb/ruby-clock/blob/main/CHANGELOG.md#migrating-from-ruby-clock-version-1-to-version-2
|
29
|
+
MESSAGE
|
30
|
+
end
|
18
31
|
end
|
19
32
|
|
20
33
|
def call_with_around_action_stack(wrappers, job_proc, job_info)
|
data/lib/ruby-clock/version.rb
CHANGED
data/lib/ruby-clock.rb
CHANGED