feat(nexus-operations): add loading state to standalone nexus operation details page#3649
Merged
Conversation
…on details page Show skeleton UI during data load instead of a blank page. Tabs are always visible since they derive from route params; only the header area and details tab content are skeletonized.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Alex-Tideman
approved these changes
Jul 8, 2026
rossedfort
enabled auto-merge (squash)
July 8, 2026 22:02
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description & motivation 💭
The standalone nexus operation details page showed a blank page between navigation and first API data load. This PR adds a skeleton loading UI so users see structural feedback immediately.
The loading skeleton is scoped appropriately: tabs are derived purely from route params (namespace, operationId, runId) and are always available, so they render immediately as real UI. Only the header area (which depends on the API response) and the details tab content area are skeletonized during load.
Two new skeleton components:
nexus-operation-header-loading.svelte— mirrors the header area (status badge, title, action buttons, detail list)nexus-operation-details-loading.svelte— mirrors the details tab content (input/output grid + card sections)The layout is restructured so back link and tabs are always visible, while header and content each independently transition from skeleton → real UI once data arrives. The loading state does not reappear when new updates to the standalone nexus operation are returned from the server via polling, only on initial load.
Screenshots (if applicable) 📸
Screen.Recording.2026-07-08.at.3.52.46.PM.mov
Design Considerations 🎨
None — follows the established skeleton pattern from #3643.
Testing 🧪
How was this tested 👻
Steps for others to test: 🚶🏽♂️🚶🏽♀️
Checklists
Draft Checklist
Merge Checklist
Issue(s) closed
Docs
Any docs updates needed?
No.