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
First of all let me start by saying this component saved me a lot of time and work, and it was exactly what I was looking for.
The only issue I could find is that the onDelete callback has inconsistent behaviour when compared to onCreate and onEdit. Both callbacks are called INSTEAD of the original code, whereas onDelete is called only after the alert with the default message ('Delete item?') as show in collectionTable.coffee:233. The correct behaviour should be to call onDelete if it is set FIRST, then proceed to the default behaviour if it is not set.
It is a very simple fix (and I can do it for you if you allow me to).
Is it possible to fix it??
Thanks in advance,
/Edson Carlotti
The text was updated successfully, but these errors were encountered:
First of all let me start by saying this component saved me a lot of time and work, and it was exactly what I was looking for.
The only issue I could find is that the onDelete callback has inconsistent behaviour when compared to onCreate and onEdit. Both callbacks are called INSTEAD of the original code, whereas onDelete is called only after the alert with the default message ('Delete item?') as show in collectionTable.coffee:233. The correct behaviour should be to call onDelete if it is set FIRST, then proceed to the default behaviour if it is not set.
It is a very simple fix (and I can do it for you if you allow me to).
Is it possible to fix it??
Thanks in advance,
/Edson Carlotti
The text was updated successfully, but these errors were encountered: