Skip to content

Conversation

@ryan953
Copy link
Member

@ryan953 ryan953 commented Dec 11, 2025

SCR-20251211-nonh

@ryan953 ryan953 requested review from a team December 11, 2025 23:22
@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Dec 11, 2025
const {data, isFetched} = useSeerOnboardingCheck();

if (!isFetched || data?.isSeerConfigured) {
return null;
Copy link
Contributor

Choose a reason for hiding this comment

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

Bug: Banner shows incorrectly when API request fails

When the useSeerOnboardingCheck API call fails, isFetched becomes true but data is undefined. The condition !isFetched || data?.isSeerConfigured evaluates to false (since undefined?.isSeerConfigured is falsy), causing the banner to display even though the actual configuration status is unknown. The component should also check isError and return null when the API request fails, to avoid showing the onboarding banner when we simply don't know whether Seer is already configured.

Fix in Cursor Fix in Web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants