ui/src/settings/ExtensionsMarketplace.vue:99-101 ("The catalogue is empty")
ui/src/settings/AgentProfilesPage.vue:56, PlaybooksPage.vue:44, CredentialBindingsPage.vue:40: these also show "No …" beside the load error, because draftValue is undefined until the form exists (ui/src/stores/settings.ts:290-292).
Done when: each view shows loading until the first read settles, then either the data, the error, or the empty state.
These views start from `[]` or `undefined` with no loaded flag, so they assert "none" before the request returns:
- `ui/src/skills/SkillsPage.vue:71` ("No skills discovered yet")
- `ui/src/curators/CuratorsPage.vue:194-198` ("No curators registered")
- `ui/src/dashboard/QuickTask.vue:93-95` ("No enabled workflows")
- `ui/src/alerts/AlertsBell.vue:46` ("No alerts")
- `ui/src/settings/ExtensionsMarketplace.vue:99-101` ("The catalogue is empty")
- `ui/src/settings/AgentProfilesPage.vue:56`, `PlaybooksPage.vue:44`, `CredentialBindingsPage.vue:40`: these also show "No …" beside the load error, because `draftValue` is undefined until the form exists (`ui/src/stores/settings.ts:290-292`).
Done when: each view shows loading until the first read settles, then either the data, the error, or the empty state.
Fixed in 820beda7 and pushed. Each listed view now tracks whether the first read has settled: Skills, Curators, QuickTask, AlertsBell (shared loaded flag in use-alerts) and the extensions catalogue (catalogueLoaded) show a loading state until then, then data/error/empty. AgentProfiles, Playbooks and CredentialBindings show their empty state only once the draft exists (was: beside the load error). Verified: task check passed on the committed tree (one v-else-if chain fixed during iteration).
Fixed in 820beda7 and pushed. Each listed view now tracks whether the first read has settled: Skills, Curators, QuickTask, AlertsBell (shared loaded flag in use-alerts) and the extensions catalogue (catalogueLoaded) show a loading state until then, then data/error/empty. AgentProfiles, Playbooks and CredentialBindings show their empty state only once the draft exists (was: beside the load error). Verified: task check passed on the committed tree (one v-else-if chain fixed during iteration).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
These views start from
[]orundefinedwith no loaded flag, so they assert "none" before the request returns:ui/src/skills/SkillsPage.vue:71("No skills discovered yet")ui/src/curators/CuratorsPage.vue:194-198("No curators registered")ui/src/dashboard/QuickTask.vue:93-95("No enabled workflows")ui/src/alerts/AlertsBell.vue:46("No alerts")ui/src/settings/ExtensionsMarketplace.vue:99-101("The catalogue is empty")ui/src/settings/AgentProfilesPage.vue:56,PlaybooksPage.vue:44,CredentialBindingsPage.vue:40: these also show "No …" beside the load error, becausedraftValueis undefined until the form exists (ui/src/stores/settings.ts:290-292).Done when: each view shows loading until the first read settles, then either the data, the error, or the empty state.
Fixed in
820beda7and pushed. Each listed view now tracks whether the first read has settled: Skills, Curators, QuickTask, AlertsBell (shared loaded flag in use-alerts) and the extensions catalogue (catalogueLoaded) show a loading state until then, then data/error/empty. AgentProfiles, Playbooks and CredentialBindings show their empty state only once the draft exists (was: beside the load error). Verified: task check passed on the committed tree (one v-else-if chain fixed during iteration).Fixed in
820beda7and pushed to main. Gate: task check exited 0 on the committed tree.