GH-1688 - Add seconds and hours to moment granularity#1689
Open
ambition-consulting wants to merge 1 commit into
Open
GH-1688 - Add seconds and hours to moment granularity#1689ambition-consulting wants to merge 1 commit into
ambition-consulting wants to merge 1 commit into
Conversation
Signed-off-by: John-Paul Cunliffe <john@ambition.consulting>
ambition-consulting
force-pushed
the
feature/GH-1688
branch
from
d024ffe to
5b20255
Compare
Member
|
I wonder if we should change the setup of the scheduled jobs to be contributed from auto-configuration and not by annotations. This would allow us to set up the more frequent ones only if the corresponding frequency is activated in the configuration. Otherwise, we will now trigger a code execution every second without a need for that now. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I understand the original article advices against it - but for some domains time-based events just happen more frequently, and being able to listen to such fine-grained time events is feasible.