Files Inspector lists need retry actions after request failures #885

Open
opened 2026-10-02 17:33:25 +00:00 by kayg · 0 comments
Owner

Evidence

The Files Inspector loads version history and linked notes when the selected item changes. Both requests set an error message on failure. Neither section has a Retry action, so the User must leave and reopen the item or reload the page to try again.

  • apps/web/src/lib/files/InfoPanel.svelte:92-105,126-142
  • apps/web/src/lib/files/InfoPanel.svelte:239-278

Expected behaviour

Show a Retry action for each failed request. Retry only that section and keep other inspector data visible.

Owner rule

The UX-completeness rule requires each error state to give the User a way forward.

Test idea

Make the version request and linked-notes request fail once, then succeed. Verify each section exposes Retry and loads its own results after the action.

## Evidence The Files Inspector loads version history and linked notes when the selected item changes. Both requests set an error message on failure. Neither section has a Retry action, so the User must leave and reopen the item or reload the page to try again. - `apps/web/src/lib/files/InfoPanel.svelte:92-105,126-142` - `apps/web/src/lib/files/InfoPanel.svelte:239-278` ## Expected behaviour Show a Retry action for each failed request. Retry only that section and keep other inspector data visible. ## Owner rule The UX-completeness rule requires each error state to give the User a way forward. ## Test idea Make the version request and linked-notes request fail once, then succeed. Verify each section exposes Retry and loads its own results after the action.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
kayg/calternal#885
No description provided.