ref(alerts): drop SystemAlerts from the init queue component map#115223
Merged
evanpurkhiser merged 1 commit intoMay 11, 2026
Conversation
evanpurkhiser
requested review from
JonasBa,
billyvg and
markstory
and removed request for
a team
github-actions
Bot
added
the
Scope: Frontend
Contributor
📊 Type Coverage Diff✅ No new type safety issues introduced. Coverage: 93.46% |
markstory
approved these changes
May 11, 2026
Member
|
@evanpurkhiser 🧼 thank you! |
evanpurkhiser
force-pushed
the
evanpurkhiser/ref-alerts-drop-systemalerts-from-the-init-queue-component-map
branch
from
328fcee to
3287904
Compare
Backend partial/alerts.html no longer pushes a SystemAlerts renderReact config (see prior commit). Remove the matching frontend entry from COMPONENT_MAP, the SentryInitRenderReactComponent enum, and the corresponding test.
evanpurkhiser
force-pushed
the
evanpurkhiser/ref-alerts-drop-systemalerts-from-the-init-queue-component-map
branch
from
3287904 to
872c5d9
Compare
evanpurkhiser
deleted the
evanpurkhiser/ref-alerts-drop-systemalerts-from-the-init-queue-component-map
branch
dashed
pushed a commit
that referenced
this pull request
May 11, 2026
…5223) The Django template `partial/alerts.html` no longer pushes a `SystemAlerts` `renderReact` config onto `window.__onSentryInit` (see #115222). Drop the corresponding frontend entry from `processInitQueue`'s `COMPONENT_MAP`, the `SentryInitRenderReactComponent` enum, and the now-orphaned test. The standalone `<SystemAlerts>` mount has been dead plumbing since the React/Reflux era began in 2015 — see the linked backend PR for the full history trek. Every `AlertStore` producer lives inside the SPA's `<App>` tree, which renders its own `<SystemAlerts>`. `SystemAlerts` itself stays — only its registration in the init queue is removed. The component continues to be mounted in-tree by `appBodyContent.tsx` and `organizationLayout/index.tsx`.
nikkikapadia
pushed a commit
that referenced
this pull request
May 12, 2026
…5223) The Django template `partial/alerts.html` no longer pushes a `SystemAlerts` `renderReact` config onto `window.__onSentryInit` (see #115222). Drop the corresponding frontend entry from `processInitQueue`'s `COMPONENT_MAP`, the `SentryInitRenderReactComponent` enum, and the now-orphaned test. The standalone `<SystemAlerts>` mount has been dead plumbing since the React/Reflux era began in 2015 — see the linked backend PR for the full history trek. Every `AlertStore` producer lives inside the SPA's `<App>` tree, which renders its own `<SystemAlerts>`. `SystemAlerts` itself stays — only its registration in the init queue is removed. The component continues to be mounted in-tree by `appBodyContent.tsx` and `organizationLayout/index.tsx`.
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
3 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.
The Django template
partial/alerts.htmlno longer pushes aSystemAlertsrenderReactconfig ontowindow.__onSentryInit(see #115222). Drop the corresponding frontend entry fromprocessInitQueue'sCOMPONENT_MAP, theSentryInitRenderReactComponentenum, and the now-orphaned test.The standalone
<SystemAlerts>mount has been dead plumbing since the React/Reflux era began in 2015 — see the linked backend PR for the full history trek. EveryAlertStoreproducer lives inside the SPA's<App>tree, which renders its own<SystemAlerts>.SystemAlertsitself stays — only its registration in the init queue is removed. The component continues to be mounted in-tree byappBodyContent.tsxandorganizationLayout/index.tsx.