fix(settings): invalidate cache in notification settings#112161
Merged
natemoo-re merged 4 commits intomasterfrom Apr 3, 2026
Merged
fix(settings): invalidate cache in notification settings#112161natemoo-re merged 4 commits intomasterfrom
natemoo-re merged 4 commits intomasterfrom
Conversation
github-actions
bot
added
the
Scope: Frontend
TkDodo
approved these changes
Apr 3, 2026
…ttings.tsx Co-authored-by: Dominik Dorfmeister 🔮 <dominik.dorfmeister@sentry.io>
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Some notification settings were not updating the underlying data on success, leading to the form being reset with stale
initialData. In effect, the form appeared to not trigger any update from the frontend—a hard refresh would display the correct values because the backend did process the update.Closes DE-1043, closes #112143