This repository has been archived by the owner on Sep 11, 2024. It is now read-only.
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.
Replace uses of
checkDeviceTrust
withgetDeviceVerificationStatus
#10663Replace uses of
checkDeviceTrust
withgetDeviceVerificationStatus
#10663Changes from 10 commits
4dffcf6
f706559
6c6fe7f
432e293
ef47246
9d2d47b
edfad2b
74d5696
3c88d94
1cc6e40
8b72ebf
02f8263
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
To match L177 in the same file
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.
The problem here is avoiding the implicit cast to boolean if
deviceTrust
is nullish. We could do something likeisVerified = !!(isMe ? deviceTrust?.crossSigningVerified : deviceTrust?.isVerified()))
but I'm far from convinced that's clearer.At L177, we have an explicit check on
deviceTrust
, so I'd say my variant of this is closer to L177 than yours.