oxidecomputer / oxidecomputer/console
Loading skeleton could include more of the real UI
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 228
- Forks
- 22
- Avg merge
- 19h 42m
- Merged PRs (30d)
- 32
Description
Not sure it's worth the effort, but a lot of the top bar and sidebar could be displayed even before the loaders come back — definitely the breadcrumbs, the sidebar links, the system-silo picker. The hard part is that RR only lets you define a HydrateFallback, so we can't let each layout (system, silo, project, etc) define its own fallback using its own logic. It would be sad to have to have an if-else chain in the root HydrateFallback that uses the path to decide which layout to render, but I guess we could make it work.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the root HydrateFallback and the system, silo, and project layout components. Determine how breadcrumbs, sidebar links, and the system-silo picker could render before loaders complete without relying on an unclear path-based if-else chain. Done means the loading skeleton includes the specified UI across the relevant layouts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100