Do not calculate highlight notifs for threads unknown to the room #2957
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.
Hugely helps with element-hq/element-web#23921
This should fully go away with things like MSC3874.
Threaded events are sent down
/sync
and are considered threaded events by the code that fixes notifications for encrypted rooms. However, if the thread root has not been discovered then the thread model does not exist yet and the optional chaining operator would make thehasUserReadEvent
variableundefined
who then got casted to a falsy value...Checklist
Here's what your changelog entry will look like:
🐛 Bug Fixes