[COMPASS-1901] Implement CRUD loading spinners/ripples/animations Created: 04/Sep/17 Updated: 27/Oct/23 Resolved: 01/Oct/18 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | CRUD, Performance |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Peter Schmidt | Assignee: | Unassigned |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Epic Link: | COMPASS-1739 |
| Story Points: | 3 |
| Description |
|
Add loading spinners in places known to be slow. Scenario1. Visit data.mongodb.parts Issue 1Fetching data from the server can take an unbounded amount of time (e.g. server never responds, server under a DDoS attack, rogue queries, etc). Solution: Reuse the existing loading spinner for loading more documents: Issue 2See Example with 110,592 fields (48^3): Issue 3As rendering can take a long time, the naive fix here is to let the user know it can take a long time with a rendering/loading text or spinner, depending on whether the UI is locked. Aside: Longer term, getting field-based updates to work would allow the user to project only the fields they care about and then update just those fields, but there are no current plans to implement this. Aside 2: This issue only affects edit mode, where the user has double-clicked on the specific field they wish to edit. Specifically clone, loading, cancel, update success and delete can all drop back to rendering just 25 fields, as they have no specific requirement to maintain the user's current context, and so are not affected. Aside 3: Table view (COMPASS-652) if it got filtering of fields may also resolve this, as might adding a filter fields box into CRUD itself. |
| Comments |
| Comment by Durran Jordan [ 01/Oct/18 ] |
|
Rewriting stories to remove hadron-document |
| Comment by Peter Schmidt [ 04/Sep/17 ] |
|
Refocused this issue on the easier loading spinners (3 story points), broke the 100k (developer-configurable) field limit into |