Reordable not enabling on relationship repeater
I'm building a nested relationship and i'm having a issue where the reordable settings are completely ignored if i set a relationship on the repeater field.
Each model involved is using the spatie/eloquent-sortable package.
Right now i have
Page
model which has a series of ContentFields
attached to it through a hasMany relationship
this works perfectly fine and i can reorder the elements with drag and drop and buttons.
I have also setup the blocks to have a HasMany relationship to ContentFieldPromo
model which is a pivot from which i can attach a Promo
model to it so i can make the repeater field compatible indirectly with a belongsToMany Relationship,
this works as expected in every other part of the application where i setup something similar however in this specific case filament is ignoring the reordable settings on the repeater
I can confirm the field works properly since i can add and remove items but i can't reorder. Disabling the relationship makes the field enable reordering.
6 Replies
Anyone ? I have no idea if it's an issue related to something wrong i did or it's a limitation of filament itself
As a clutch I tried to replace the native Repeater field with the TableRepeater from Awcodes and the reorder is working properly
This leads me to believe there's a bug with the Repeater field for this specific edge case.


I think it's being your using a grid
I did try to remove the grid but the result was still the same
Strange could be a sub nesting issue. Can you create a reproduction repo and submit a GH Issue?
Situation is a bit hectic since we are nearing release, I will try as soon as I am able.