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 have a model which uses the SoftDeletes trait and the SortableTrait. On the front-end of my app I'm displaying only the ordered non-trashed models, but on the back-end I'm including the trashed models, which can be reordered.
The soft deleting trait adds a constraint when the setNewOrder method is looping over the ids, therefore the order column is updated only on the non-trashed models. This is a bug because the new order is not synced across all the given models, which gives us duplicate order numbers, and that leads to unexpected results.
I'm happy to submit a PR if this is something that should be fixed. Thanks!
The text was updated successfully, but these errors were encountered:
I have a model which uses the
SoftDeletes trait
and theSortableTrait
. On the front-end of my app I'm displaying only the ordered non-trashed models, but on the back-end I'm including the trashed models, which can be reordered.The soft deleting trait adds a constraint when the
setNewOrder
method is looping over the ids, therefore the order column is updated only on the non-trashed models. This is a bug because the new order is not synced across all the given models, which gives us duplicate order numbers, and that leads to unexpected results.I'm happy to submit a PR if this is something that should be fixed. Thanks!
The text was updated successfully, but these errors were encountered: