Unify verification event processing in Crypto V2 #1717
Merged
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.
Previously the
CryptoSDK
would automatically handle encrypted verification events in rooms as soon as they are decrypted viadecryptRoomEvent
methods. Whilst this sounds convenient, there are a number of issues with this approach:An improved approach is to prevent the machine from automatically processing verification events via a parameter, and then reuse existing event observers to pass in both encrypted and unencrypted verification events.