mariusticha
Persist toggleable column state between sessions
alright now i understand what your looking for. i've done a little research on this and i haven't found a built in functionality for this use case.
what i've found is the part in the app where the visible columns are determined. that should be this method here:
https://github.com/filamentphp/filament/blob/3.x/packages/tables/src/Table/Concerns/HasColumns.php#L101
13 replies
Select afterStateUpdated does not fire when selection is cleared
i even get the expected results in an example where the second input is a datepicker and its value is only set to zero if the value of the select is 1:
`
bringing me these logs:
and everything looks as expected in the browser.
25 replies
Select afterStateUpdated does not fire when selection is cleared
i did a little research in this case and apparently the solution is slightly different.
the crucial difference between your first and your second example is not that you set the second component to live (and it's also not about whether native is set to true or false, as i suggested). the problem in your first example is the dd() in afterStateUpdated. this stops the execution before the roundtrip is completely finished, leaving the app in an inconsistent state between server and client.
25 replies
Persist toggleable column state between sessions
i'm not sure if i understand your problem exactly, but is maybe this what you're looking for?
https://filamentphp.com/docs/3.x/tables/columns/getting-started#making-toggleable-columns-hidden-by-default
13 replies