Render an invite that arrives as a timeline member event as an invite push - #7208
Open
ara4n wants to merge 1 commit into
Open
Render an invite that arrives as a timeline member event as an invite push#7208ara4n wants to merge 1 commit into
ara4n wants to merge 1 commit into
Conversation
… push An invite for the current user can resolve as a timeline member event rather than a stripped invite when the room has already advanced past the invited state by notification-resolution time — e.g. the server auto-joined the user because their knock was accepted (element-hq/synapse#16307). Such invites were filtered out of notifications entirely; render them with the normal invite copy instead. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Uk8aPxHn3BHCe52L226jdG
|
This file contains hidden or 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
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.



An invite for the current user can resolve as a timeline member event rather than a stripped invite when the room has already advanced past the invited state by notification-resolution time — e.g. the server auto-joined the user because their knock was accepted (element-hq/synapse#16307). Such invites were filtered out of notifications entirely; render them with the normal invite copy instead.
Tests
e2e rig flow 10
Tested devices
Checklist