Skip to content

Render folder studio progressively#138

Merged
cbusillo merged 1 commit into
mainfrom
fix-folder-studio-progressive-render
Jun 6, 2026
Merged

Render folder studio progressively#138
cbusillo merged 1 commit into
mainfrom
fix-folder-studio-progressive-render

Conversation

@cbusillo

@cbusillo cbusillo commented Jun 6, 2026

Copy link
Copy Markdown
Owner

Summary

  • make the nested folder-studio route return route identity synchronously instead of blocking SvelteKit load on folder/status/host APIs
  • hydrate folder studio data client-side with typed placeholder payloads, stale-response guards, and same-route prefix refresh
  • keep the Folder Studio shell mounted during slow or failed API calls, with loading workflow copy and no enabled mutation buttons until real data arrives
  • replace invalidateAll()-dependent post-action refresh with an explicit onMutate refresh callback now that route load no longer fetches folder data

Validation

  • bash scripts/pre-commit-check.sh
  • Browser direct-opened a real /folders/<prefix> URL at http://127.0.0.1:4173 and verified the real Folder Studio surface renders
  • Playwright delayed /api/folders/... responses: before API release, .operator-shell, title, crumb, and Loading folder state were visible, with no enabled live mutation buttons; after release, the real workflow hydrated in place
  • Playwright mobile viewport 390x844: no horizontal overflow on the folder-studio route

Notes

  • This finishes the old route-loading-wall pattern for the nested folder studio path that remained after the top-level progressive rendering pass.

@cbusillo cbusillo merged commit cfd5213 into main Jun 6, 2026
5 checks passed
@cbusillo cbusillo deleted the fix-folder-studio-progressive-render branch June 6, 2026 17:45
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.

1 participant