Skip to content

[Notifier] Removed some restriction #13868

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Jun 22, 2020
Merged

[Notifier] Removed some restriction #13868

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions notifier.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -294,7 +294,7 @@ transport:
%env(SLACK_DSN)% || %env(TELEGRAM_DSN)%
</framework:chatter-transport>

<!-- Send notifications to the next scheduled transport
<!-- Send notifications to the next scheduled transport
calculated by round robin -->
<framework:chatter-transport name="slack">
%env(SLACK_DSN)% && %env(TELEGRAM_DSN)%
Expand Down Expand Up @@ -365,8 +365,7 @@ To send a notification, autowire the
The ``Notification`` is created by using two arguments: the subject and
channels. The channels specify which channel (or transport) should be used
to send the notification. For instance, ``['email', 'sms']`` will send
both an email and sms notification to the user. It is required to specify
the transport when using chatters (e.g. ``['email', 'chat/telegram']``).
both an email and sms notification to the user.

The default notification also has a ``content()`` and ``emoji()`` method to
set the notification content and icon.
Expand Down