UI Design - Filing history fails to load
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
The Filing History can be slow to load or can encounter errors when loading. This could cause confusion and is likely to generate calls.
Network calls can arise which prevent the filing history from loading. Design is required so users understand that the missing filing history is due to an issue.
We need to show a loading state that is not "You have no filings to display" while it is loading, and an error state if it fails.
Search has a loading state, but no error state
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the Filing History UI and the existing Search loading state, then trace the network request that supplies filing history. Done means loading no longer appears as an empty result, and a failed request presents a clear error state for users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- design, frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100