Skip to content

fix: add structural loading fallback to page speed monitor status lab… - #3789

Open
PATRIKA-123 wants to merge 1 commit into
bluewave-labs:developfrom
PATRIKA-123:fix/pagespeed-default-timeframe
Open

fix: add structural loading fallback to page speed monitor status lab…#3789
PATRIKA-123 wants to merge 1 commit into
bluewave-labs:developfrom
PATRIKA-123:fix/pagespeed-default-timeframe

Conversation

@PATRIKA-123

@PATRIKA-123 PATRIKA-123 commented Jul 19, 2026

Copy link
Copy Markdown

Describe your changes

Added a structural loading fallback string ("initializing") to the PageSpeedMonitorsTable status renderer. This prevents the UI component from breaking or hanging in an undefined state if a monitor's backend status returns empty or null during initial load metrics fetching.

Fixes #3772

Checklist

  • I have performed a self-reviewing and testing of my code.
  • I have included the issue # in the PR.
  • I have not included any files that are not related to my pull request.
  • I didn't use any hardcoded values.
  • My PR is granular and targeted to one specific feature.

@ajhollid ajhollid left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

This PR is just the addition of a comment?

@LvckyAPI

Copy link
Copy Markdown
Contributor

and import of useTheme

@ajhollid

Copy link
Copy Markdown
Collaborator

and import of useTheme

That was already imported? What is the purpose of this PR? The description states it adds a fallback string, am I missing something?

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

UI Bug and endless initializing

3 participants