Awesome feature!

I got one question about using the Async attribute though. Because the request now go parallel wouldn't it be possible for a previous order update be handled by the backend later then the last one being done by the user? Ending up with a different sort then expected by the user.

So in a timeline it would look like this:

User sorts cards with visitors metric in position 1 (first sort)
handleSort with visitors on position 1 gets called but is slow for some reason.
User sorts cards with visitors metric in position 0 (second sort)
First handleSort from step 2 is still going
handleSort with visitors on position 0 gets called (from step 3)
Second handleSort (step 5) finished
- Backend sets visitor metric on position 1 (second sort by user)
First handleSort (step 2) finished
- Backend sets visitor metric on position 0 (first sort by user)
Now the visitor metric is in position 0 but user expected position 1

Wouldn't synchronous requests make more sense here?

Drag and Drop Sorting