#1660 first approach to make it faster #2101
Draft
Conversation
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
1 participant
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.
attention: supersedes #2099 - needed to change base-branch afterwards - #2099 will get closed
disclaimer: don't think I've the right tools (and the experience) for kotlin to develop, but I've managed to build this locally and with these changes it was a lot faster with many recurring tasks (#1660). My proposal would be to have some additional settings where the user can enter these settings (either as double in days or in milliseconds), default should be the old settings (to avoid breaking anything). Maybe someone who is more into this project can continue here or at least point me into the right direction.
Therefore only a draft PR ...
Thanks!