-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Show the correct shield status in tooltip for more conditions #28476
base: develop
Are you sure you want to change the base?
Conversation
I think that this will need some trickery to merge this with the JS side. Obviously, this can't be merged until the JS PR is merged, since it uses values defined in that PR. But I think that when the JS side gets merged, then TypeScript will complain because the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, but I think it should match the decryption error message for that case when the trust decryption requirement is set?
break; | ||
|
||
case EventShieldReason.VERIFICATION_VIOLATION: | ||
shieldReasonMessage = _t("encryption|event_shield_reason_verification_violation"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it shoud match the existing copy for verification violation in invisible crypto? Sender's verified identity has changed
as per decryption_failure
> sender_identity_previously_verified
?
WDYT?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup, good catch. Fixed
Depends on matrix-org/matrix-js-sdk#4529
Fixes #28170
Checklist
public
/exported
symbols have accurate TSDoc documentation.