Skip to content

ref(navigation): remove hasPageFrame feature flag checks#116018

Draft
natemoo-re wants to merge 7 commits into
masterfrom
nm/page-frame/cleanup-navigation
Draft

ref(navigation): remove hasPageFrame feature flag checks#116018
natemoo-re wants to merge 7 commits into
masterfrom
nm/page-frame/cleanup-navigation

Conversation

@natemoo-re
Copy link
Copy Markdown
Member

@natemoo-re natemoo-re commented May 21, 2026

The page-frame feature flag has been 100% rolled out. This refactors useHasPageFrameFeature() callsites in views/navigation/ and eliminates dead code branches.

Removes MobileNavigation (replaced by MobilePageFrameNavigation), dead styled components (MobileNavigationLink, DesktopNavigationLink, SidebarNavigationLink, StyledReorderableFakeLink), and the legacy superuser warning block from PrimaryNavigationSidebarHeader.

The page-frame feature flag is 100% rolled out. Inline true for all
useHasPageFrameFeature() callsites and eliminate dead code branches.
@github-actions github-actions Bot added the Scope: Frontend Automatically applied to PRs that change frontend components label May 21, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 21, 2026

📊 Type Coverage Diff

✅ No new type safety issues introduced. Coverage: 93.62%

@github-actions github-actions Bot added the Scope: Backend Automatically applied to PRs that change backend components label May 21, 2026
@github-actions
Copy link
Copy Markdown
Contributor

🚨 Warning: This pull request contains Frontend and Backend changes!

It's discouraged to make changes to Sentry's Frontend and Backend in a single pull request. The Frontend and Backend are not atomically deployed. If the changes are interdependent of each other, they must be separated into two pull requests and be made forward or backwards compatible, such that the Backend or Frontend can be safely deployed independently.

Have questions? Please ask in the #discuss-dev-infra channel.

getsantry Bot and others added 2 commits May 21, 2026 17:44
The outlets need to exist for slot content to render, but they must
not be inside the test container or they break toBeEmptyDOMElement()
assertions.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant