Hi, @giant-robot Can you help me understand the idea better? Because I'm looking at the above example and I don't understand. For example, I swapped positions 3 and 7. What value will come to the reorder method?

Hey @tabuna, the current implementation will not pass arguments to the reorder method. Instead, each change will result in a POST XHR request with a payload than contains a key and an offset parameter.

key is anything you specify in the action using the key method for the item that is being dragged.
offset is the relative change in position for the same item.

You can access those directly from the request object inside the reorder method (it would be great if Request could be injected as an argument to the method when it is called).

So, for the code given above:

• If you drag the Role with id 101 2 positions down, key would be 101 and offset would be 2.
• If you drag the Role with id 101 4 positions up, key would be 101 and offset would be -4.

I hope that makes it clearer.

I like the idea of having this in a package. But I think we need to decide a few things before we release it:

• It seems to me that we won't be able to use this effectively as an action. Maybe we should better use a class inherited from a Сell.

public function columns(): array
{
    return [
        Sortable::make('method', 'string or closure'),

        ...
    ];
}

• It might be worth running this in much the same way as we do with async methods. Then we can expect pre-declared arguments in the specified method:

public function reorder(Role $role, int $offset): array
{
   //...
}

• And lastly, I think we are very much missing an example that would show how to shift not only the current model, but all the others (they also have to change their sorting index).

I will try to work with you to improve these points in the near future.

I've converted the sorting handle from an action to a Cell, as you suggest. It actually needs to be an extension of TD because of the contraints of the Table::columns method, but it seems to work fine.

Extending TD also has the benefit of being able to guess the sort key from the column name or use the render method for more complex cases. You can use it like so:

public function columns(): array
{
    return [
        ReorderHandle::make('id')
            ->method('reorder'),
        ...
    ];
}

Running the reorder method as an async method will be great. Let me know how we can achieve this.

Regarding the actual change of the sort key of the reordered models, I see your point but it feels to me like an implementation detail. There are more than one ways to do it and it really depends on the model itself.

Cheers,
George