fix: Add loading state for MetricsViewTimerange query #6759
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
closes #6646
We make a call to
MetricsViewTimerange
API in loader functions. The problem with this is we cannot add a loader state without moving the fetching out of it. While we can handle navigation from non-dashboard to dashboard page a direct visit of a dashboard doesnt start rendering until all layout and page loader functions are run.Converting the data to promises and awaiting in page component. This also means we dont have to set runtime in layout page.
Checklist: