thanks for the suggestion 🙂 this works in some cases but not for relations for example
I think I will create some model-observers to reset the fields for now
Looking at this now, and altering the state in the beforeSave looks slightly better than using an additional field I guess... thanks for thinking along though!
Didn't find a solution to this problem, but I have a "workaround": use a ViewEntry, then load a table in a new livewire component within the view. In the table I can use TextColumn which has support for the enum.