Skip to content

fix(monitors): Move edit breadcrumbs into the top bar#113272

Merged
priscilawebdev merged 11 commits into
masterfrom
priscilawebdev/fix/monitor-edit-topbar-breadcrumbs
Apr 20, 2026
Merged

fix(monitors): Move edit breadcrumbs into the top bar#113272
priscilawebdev merged 11 commits into
masterfrom
priscilawebdev/fix/monitor-edit-topbar-breadcrumbs

Conversation

@priscilawebdev

@priscilawebdev priscilawebdev commented Apr 17, 2026

Copy link
Copy Markdown
Member

Before

Screen.Recording.2026-04-17.at.11.55.18.mov

After

Screen.Recording.2026-04-17.at.11.55.45.mov

closes https://linear.app/getsentry/issue/DE-1141/monitors-doesnt-render-breadcrumbs-into-the-title-slot

Render existing monitor edit breadcrumbs through the TopBar title slot\nwhen the page-frame feature is enabled. This keeps the edit header\naligned with the newer page-frame layout without changing the legacy\nform header.\n\nCo-Authored-By: Codex <noreply@openai.com>
@github-actions github-actions Bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Apr 17, 2026
Only render the error monitor edit title and project badge in the legacy\nheader path. In page-frame mode the breadcrumb already provides the\nheader title, so leaving EditLayout.Title in place appended the monitor\nname into the top bar and left the project badge behind on its own row.\n\nCo-Authored-By: Codex <noreply@openai.com>
Skip the legacy edit header for error monitor edit pages when the\npage-frame feature is enabled. The title and feedback button already\nrender through TopBar slots in that mode, so keeping EditLayout.Header\nin place left an empty row under the top bar.\n\nCo-Authored-By: Codex <noreply@openai.com>
Keep the project context visible on the error monitor edit page in\npage-frame mode by rendering the project badge alongside the breadcrumb\nin the top bar title area.\n\nCo-Authored-By: Codex <noreply@openai.com>
Align the error monitor edit page with the existing metric monitor\npage-frame layout by rendering the monitor name in the top bar title\nslot instead of keeping the project badge there.\n\nCo-Authored-By: Codex <noreply@openai.com>
priscilawebdev and others added 2 commits April 17, 2026 11:36
Render the error monitor edit breadcrumb in page-frame mode as a\nsettings-style project path: Monitors / Error / <project> / Configure.\nThis keeps the project context visible without leaving a separate badge\nrow or mixing the project into the monitor title.\n\nCo-Authored-By: Codex <noreply@openai.com>
Use the same project-aware top bar breadcrumb on the error monitor detail and edit pages when page-frame is enabled.

Keep the legacy header path unchanged so this stays scoped to the new top bar layout.

Co-Authored-By: OpenAI Codex <noreply@openai.com>
Make the project crumb in the error monitor edit breadcrumb navigate back to the detail view.

Keep the detail breadcrumb itself as the current location.

Co-Authored-By: OpenAI Codex <noreply@openai.com>
Keep the error monitor detail and edit breadcrumbs local to their pages instead of sharing a helper.

The detail and edit paths now own their slightly different breadcrumb behavior directly.

Co-Authored-By: OpenAI Codex <noreply@openai.com>
Inline the error monitor detail and edit breadcrumb markup where it is used instead of keeping small local wrapper components.

This keeps the page-frame-only breadcrumb variants directly next to their slots.

Co-Authored-By: OpenAI Codex <noreply@openai.com>
@linear-code

linear-code Bot commented Apr 17, 2026

Copy link
Copy Markdown

Reuse the edit route's resolved project instead of looking it up again inside the error monitor edit components.

This makes the project requirement explicit and removes the defensive breadcrumb guard from the page-frame edit header.

Co-Authored-By: OpenAI Codex <noreply@openai.com>
@priscilawebdev

Copy link
Copy Markdown
Member Author

bugbot run

@cursor cursor Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

Reviewed by Cursor Bugbot for commit 843bcdc. Configure here.

return <EditExistingUptimeDetectorForm detector={detector} />;
case 'error':
return <EditExistingErrorDetectorForm detector={detector} />;
return <EditExistingErrorDetectorForm detector={detector} project={project} />;

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree this is a little awkward since only this form uses project. The main reason I did it this way is that the route already guarantees a project, so passing it down lets us remove the defensive undefined checks from the form and keep the breadcrumb/rendering logic simpler. I don’t feel strongly about it though, and I’m happy to adjust if you’d prefer a different shape

@priscilawebdev
priscilawebdev marked this pull request as ready for review April 17, 2026 11:02
@priscilawebdev
priscilawebdev requested a review from a team as a code owner April 17, 2026 11:02
@priscilawebdev
priscilawebdev requested a review from a team April 17, 2026 11:02
@priscilawebdev
priscilawebdev merged commit 1673641 into master Apr 20, 2026
65 checks passed
@priscilawebdev
priscilawebdev deleted the priscilawebdev/fix/monitor-edit-topbar-breadcrumbs branch April 20, 2026 08:08
@github-actions github-actions Bot locked and limited conversation to collaborators May 5, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants