Skip to content
This repository was archived by the owner on Sep 11, 2024. It is now read-only.

Devtools for stuck notifications #10042

Merged
merged 12 commits into from
Feb 3, 2023

Conversation

germain-gg
Copy link
Contributor

@germain-gg germain-gg commented Feb 1, 2023

Fixes element-hq/element-web#24388

I have not written tests yet as I'm not sure everything in here warrants to be tested

/devtools -> Notifications debug

Screenshot 2023-02-01 at 12 00 35

Checklist

  • Tests written for new code (and old code if feasible)
  • Linter and other CI checks pass
  • Sign-off given on the changes (see CONTRIBUTING.md)

This change is marked as an internal change (Task), so will not be included in the changelog.

@germain-gg germain-gg added the T-Task Refactoring, enabling or disabling functionality, other engineering tasks label Feb 1, 2023
@germain-gg germain-gg changed the title gsouquet/devtools stucknotifications Devtools for stuck notifications Feb 1, 2023
@weeman1337
Copy link
Contributor

Tested with this case

image

Would that help? You can see, that it thinks the reaction is the last event in the thread. But actually there is another message.

@germain-gg

This comment was marked as off-topic.

@germain-gg germain-gg marked this pull request as ready for review February 1, 2023 16:13
@germain-gg germain-gg requested a review from a team as a code owner February 1, 2023 16:13
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
T-Task Refactoring, enabling or disabling functionality, other engineering tasks
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Stuck notifications: Create devtools room stuck notifications debug tool
3 participants