Timeline: Update the human readable description for the SentInClear shield. #3805
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
pixlwave
requested review from
stefanceriu and
BillCarsonFr
and removed request for
a team
pixlwave
force-pushed
the
doug/sent-in-clear-message
branch
from
656197e to
5c185a5
Compare
andybalaam
approved these changes
Aug 6, 2024
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #3805 +/- ##
==========================================
- Coverage 84.11% 84.10% -0.01%
==========================================
Files 263 263
Lines 27476 27476
==========================================
- Hits 23111 23109 -2
- Misses 4365 4367 +2 ☔ View full report in Codecov by Sentry. |
pixlwave
force-pushed
the
doug/sent-in-clear-message
branch
from
5c185a5 to
7586b3d
Compare
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.
The new message is more understandable in the timeline context and is consistent with current implementations (Element Web)