You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using a crudManager to manage data handling with the backend. When a load request is still pending while initiating a new load request, the crudManager correctly cancels the pending request. However it also prints an error message to the console.
I wonder if this is intended behaviour? It seems odd to me, that a correctly canceled request causes an error message to be printed.
In our scenario, a scheduler always spans the duration of a day and we have controls for the user to navigate to the previous/next day. When the user clicks quickly, load requests are regularly cancelled before they are fulfilled by the server. Is there any way to suppress these error messages?
Attached you find a video demonstrating the described behaviour.
Screen Recording 2025-03-26 at 15.08.39.mov
(6.11 MiB) Downloaded 2 times
The text was updated successfully, but these errors were encountered:
SergeyMaltsev
added
resolved
Fixed but not yet released (available in the nightly builds)
and removed
resolved
Fixed but not yet released (available in the nightly builds)
labels
Apr 1, 2025
Forum post
I'm using a crudManager to manage data handling with the backend. When a load request is still pending while initiating a new load request, the crudManager correctly cancels the pending request. However it also prints an error message to the console.
I wonder if this is intended behaviour? It seems odd to me, that a correctly canceled request causes an error message to be printed.
In our scenario, a scheduler always spans the duration of a day and we have controls for the user to navigate to the previous/next day. When the user clicks quickly, load requests are regularly cancelled before they are fulfilled by the server. Is there any way to suppress these error messages?
Attached you find a video demonstrating the described behaviour.
The text was updated successfully, but these errors were encountered: