-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: notification scheduler #56
Merged
Conversation
This file contains 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
jsonmaf1a
force-pushed
the
scheduler
branch
2 times, most recently
from
December 11, 2024 15:50
7a7a2c5
to
3c6ef74
Compare
JarKz
requested changes
Dec 12, 2024
crates/backend/src/scheduler.rs
Outdated
Comment on lines
41
to
46
let datetime_formats = [ | ||
"%d.%m.%Y %H:%M", // 01.01.2025 00:00 | ||
"%Y-%m-%d %H:%M", // 01-01-2025 00:00 | ||
"%d.%m.%Y %I:%M %p", // 01.01.2025 12:00 AM | ||
"%Y-%m-%d %I:%M %p", // 01-01-2025 12:00 AM | ||
]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The second and last are not matched to examples in commentaries. The second will match only "2025-01-01 00:00" and the last one will match only "2025-01-01 12:00 AM".
JarKz
approved these changes
Dec 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull-request implements the feature discussed in #32
It adds support for scheduling notifications with the
--schedule
flag in thesend
command.Supported Date and Time Formats:
%d.%m.%Y %H:%M
— 01.01.2025 00:00%d-%m-%Y %H:%M
— 01-01-2025 00:00%Y.%m.%d %H:%M
— 2025.01.01 00:00%Y-%m-%d %H:%M
— 2025-01-01 00:00%d.%m.%Y %I:%M %p
— 01.01.2025 12:00 AM%d-%m-%Y %I:%M %p
— 01-01-2025 12:00 AM%Y.%m.%d %I:%M %p
— 2025.01.01 12:00 AM%Y-%m-%d %I:%M %p
— 2025-01-01 12:00 AM%H:%M
— 18:45%I:%M %p
— 06:45 PMRFC 3339
/ISO 8601
UTC stringUsage: