Skip to content

Conversation

ClearlyClaire
Copy link
Contributor

@ClearlyClaire ClearlyClaire commented Aug 1, 2024

Choosing to dismiss a notification request synchronously deletes the record, but accepting waits for the notifications to be (asynchronously) merged back into the timeline for it to be deleted, which can result in a really confusing experience.

That being said, there is a broader issue with how accepted notification requests get merged, as this happens asynchronously and is not reflected into the interface unless the notifications feed is reloaded.

(This is still a draft because the whole worker lacks tests)

@ClearlyClaire ClearlyClaire force-pushed the fixes/asynchronous-notification-request-acceptance branch from d21044a to ab7344f Compare August 1, 2024 21:15
@ClearlyClaire ClearlyClaire force-pushed the fixes/asynchronous-notification-request-acceptance branch from ab7344f to 65ff208 Compare August 2, 2024 09:25
@ClearlyClaire ClearlyClaire marked this pull request as ready for review August 2, 2024 09:25
@ClearlyClaire ClearlyClaire requested review from renchap and a team August 13, 2024 12:25
@ClearlyClaire ClearlyClaire added this pull request to the merge queue Aug 14, 2024
Merged via the queue into main with commit 7996a95 Aug 14, 2024
32 checks passed
@ClearlyClaire ClearlyClaire deleted the fixes/asynchronous-notification-request-acceptance branch August 14, 2024 07:44
justinwritescode pushed a commit to justinwritescode/mastodon that referenced this pull request Sep 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants