-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Description
New Issue Checklist
- I am not disclosing a vulnerability.
- I am not just asking a question.
- I have searched through existing issues.
- I can reproduce the issue with the latest versions of Parse Server and Parse Dashboard.
Issue Description
A long-loading request is not cancelled when changing the sorting field in the data browser. This causes the result of the long-loading request overwriting the result of the currently displayed data, while the field sorting indicator still shows the current sorting.
This is similar to #2671, it may be a separate issue or that the bug was not fixed completely.
Steps to reproduce
- Navigate to data browser.
- In a class with many objects where
fieldA
is an indexed field andfieldB
is a non-indexed field. - Click on header cell to sort by
fieldB
, then immediately on header cell to sort byfieldA
. - The results sorted by
fieldA
are displayed immediately. - When the long-loading request sorted by
fieldB
finished, it will overwrite the results in the data browser while the header row still shows sorted byfieldA
.
Expected Outcome
The long-longing request sorted by fieldB
should be cancelled.
If possible, not only should the results not be displayed, but the HTTP request should be cancelled, so the server knows that the client doesn't need the response anymore and avoids sending the response unnecessarily. This doesn't require any changes in Parse Server, it's managed by the underlying HTTP library on the server side.
Environment
Dashboard
- Parse Dashboard version:
7.2.0-alpha.3