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
There is a general problem with the tables (initially thought it's related to enums) - something about the timings of the fetch data we assume.
This is the error:
And it can be simulated in several ways:
On your side - https://www.laravel-enso.com/administration/XXXX - click rapidly ( as fast as you say out loud, normally, click click click :) ) on the Administration menus - I start from Users -> User Groups -> .... -> Teams.
On our side we have some second tables that open when a clickable column cell is clicked on the first table. The same thing happens, when multiple initTable + tableData are triggered, we get the same error.
We tried an initial investigation and played a bit with $nextTink and _debounce, but I feel that this is not the right solution. (A debounce of 500ms on click will avoid the issue).
Investigation is still ongoing on our side. If you have some ideas/fixes would be great.
Thanks!
The text was updated successfully, but these errors were encountered:
This is a bug.
Prerequisites
(enso is made of many specialized packages: https://github.com/laravel-enso)
Hi,
There is a general problem with the tables (initially thought it's related to
enums
) - something about the timings of the fetch data we assume.This is the error:
And it can be simulated in several ways:
On your side - https://www.laravel-enso.com/administration/XXXX - click rapidly ( as fast as you say out loud, normally, click click click :) ) on the Administration menus - I start from Users -> User Groups -> .... -> Teams.
On our side we have some second tables that open when a clickable column cell is clicked on the first table. The same thing happens, when multiple
initTable
+tableData
are triggered, we get the same error.We tried an initial investigation and played a bit with $nextTink and _debounce, but I feel that this is not the right solution. (A debounce of 500ms on click will avoid the issue).
Investigation is still ongoing on our side. If you have some ideas/fixes would be great.
Thanks!
The text was updated successfully, but these errors were encountered: