Skip to content

ref(seer): Extract explorer sessions into a shared React context#115515

Open
JonasBa wants to merge 2 commits into
masterfrom
jb/seer/sessions-context
Open

ref(seer): Extract explorer sessions into a shared React context#115515
JonasBa wants to merge 2 commits into
masterfrom
jb/seer/sessions-context

Conversation

@JonasBa
Copy link
Copy Markdown
Member

@JonasBa JonasBa commented May 13, 2026

Replace useExplorerSessions with a dedicated top level provider. This makes sessions and history app wide, opens the door for parallel chats and different improvement in the future.

@JonasBa JonasBa requested a review from a team as a code owner May 13, 2026 21:28
@github-actions github-actions Bot added the Scope: Frontend Automatically applied to PRs that change frontend components label May 13, 2026
@JonasBa JonasBa requested a review from aliu39 May 13, 2026 21:30
Comment thread static/app/views/seerExplorer/seerExplorerSessionContext.tsx
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 13, 2026

📊 Type Coverage Diff

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

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

should filename be lowercase

Comment thread static/app/views/seerExplorer/seerExplorerSessionContext.tsx
@JonasBa JonasBa force-pushed the jb/seer/sessions-context branch from 38af97f to 1b6a7e5 Compare May 13, 2026 22:00
@JonasBa JonasBa requested a review from a team as a code owner May 13, 2026 22:00
@github-actions github-actions Bot added the Scope: Backend Automatically applied to PRs that change backend components label May 13, 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.

Copy link
Copy Markdown
Contributor

@cursor cursor Bot left a comment

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 50534fc. Configure here.

import {isSeerExplorerEnabled} from 'sentry/views/seerExplorer/utils';

function useSeerExplorerSessionsQuery({
limit = 10,
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.

Default session limit reduced from 20 to 10

Low Severity

The default limit parameter in useSeerExplorerSessionsQuery is 10, reduced from the previous value of 20 used in the deleted useExplorerSessions hook. The SeerExplorerSessionsProvider currently overrides this with limit: 20, so runtime behavior is preserved. However, the misleading default could cause a regression if the function is ever called without an explicit limit. As noted in the PR discussion, this reduction was not intentional.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 50534fc. Configure here.

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.

2 participants