Unify events text #16131
Merged
Unify events text #16131
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
ncounter
force-pushed
the
unify-text-for-subscriptions
branch
2 times, most recently
from
fea7bc5
to
bec5907
Compare
ncounter
force-pushed
the
unify-text-for-subscriptions
branch
from
c1b7776
to
655fef7
Compare
ncounter
force-pushed
the
unify-text-for-subscriptions
branch
from
655fef7
to
069a9b8
Compare
eduardoj
approved these changes
May 15, 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.
Be consistent in Notifications' text events.
Title
Try to be as closest as possible in the Notification's title:
description(AKA notification's configuration title)subject(AKA notification's email subject)Before it was a mix of:
After it is only:
Description
Align
explanationtext (AKA notification's configuration description)Before it was a mix of:
After it is only: