-
Notifications
You must be signed in to change notification settings - Fork 20
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
Implement modularized notification system #61
base: main
Are you sure you want to change the base?
Implement modularized notification system #61
Conversation
- Abstracted notification specifics out of `runSimulation`. - Added `notifier` parameter to `runSimulation` to use specific notifiers. - Added support for multiple notifiers to be used simultaneously. - Moved notification handling to `notifications.R`. - Added `Notifier` S3 class to represent notifiers. - Added `TelegramNotifier` and `PushbulletNotifier` S3 classes. - Added `new_TelegramNotifier` and `new_PushbulletNotifier` constructors. - Updated documentation to reflect changes in notification handling.
@philchalmers since I dont use pushbullet it would be nice if you could test if it works :) |
@philchalmers did you intend that one may also pass notification = c("condition", "complete")? |
This looks really nice, thanks for the contribution! Looks nicer than my previous pushbullet approach (I don't use that much anyway as larger simulation typically get submitted to SLURM clusters, but this is nice nevertheless). Could you a) remove the |
runSimulation
.notifier
parameter torunSimulation
to use specific notifiers.notifications.R
.Notifier
S3 class to represent notifiers.TelegramNotifier
andPushbulletNotifier
S3 classes.new_TelegramNotifier
andnew_PushbulletNotifier
constructors.