You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to create a system where the notifications can't be turned off (you'll see them in the header), but you can add additional ways to get the notifications, for example email or push notification to a companion app. All I can do right now is turn on / off ActivityNotification.config.subscribe_as_default which will either turn on all or none of the notification strategies.
Expected solution
It would be nice if you could configure subscribe_to_email_as_default and subscribe_to_optional_targets_as_default. Leaving them out from the config file would fall back to the existing config.
ActivityNotification.configuredo |config|
## Show in-app notifications by defaultconfig.subscribe_as_default=true## Don't send out emails before the user allows itconfig.subscribe_to_email_as_default=false## Subscribe to slack, amazon_sns, etc by default, but not to firebase_pushconfig.subscribe_to_optional_targets_as_default=[:slack,:amazon_sns,:etc]## or turn on all optional targets as default# config.subscribe_to_optional_targets_as_default = true## or turn off all optional targets as default# config.subscribe_to_optional_targets_as_default = falseend
Alternatives
I was thinking about creating a default subscription entity for all users, but that would be the opposite of having defaults.
The text was updated successfully, but these errors were encountered:
Problem or use case
I'm trying to create a system where the notifications can't be turned off (you'll see them in the header), but you can add additional ways to get the notifications, for example email or push notification to a companion app. All I can do right now is turn on / off
ActivityNotification.config.subscribe_as_default
which will either turn on all or none of the notification strategies.Expected solution
It would be nice if you could configure
subscribe_to_email_as_default
andsubscribe_to_optional_targets_as_default
. Leaving them out from the config file would fall back to the existing config.Alternatives
I was thinking about creating a default subscription entity for all users, but that would be the opposite of having defaults.
The text was updated successfully, but these errors were encountered: