Samus_Aran
Problems closing a parent modal
I still would be interested in an answer, but I found a workaround that is sufficient for my use case:
First I was using the feature described here: https://filamentphp.com/docs/3.x/actions/modals#adding-an-action-to-custom-modal-content. This way I could register a proper DeleteAction and at least pass it to the modal blade View.
I then removed the Section Component from my infolist and instead wrapped the whole InfoList-Livewire-Component in Filaments Section Blade Component: https://filamentphp.com/docs/3.x/support/blade-components/section. There I could place the Action buttons using the endHeader Slot.
I ended up with the identical looking UI, but my Actions are now definied within the ViewAction and passed down to the modalContent.
2 replies
Using an Infolist-Action with another infolist in it.
@krekas Yes, I have an Infolist and I want to use a prefixAction on a TextEntry to open a modal that contains another infolist with more information.
And since i have the infolist() method available on this Action to pass an infolist into it, I would assume that there should also be a way to provide the data to the infolist
12 replies
Use recordAction() In a Table Widget
@awcodes Yes it looks like it. I am currently toying around with this and it seems like whatever Action I put into recordAction() needs to be also present in actions() of the table. So it seems that I need to hide it with CSS
19 replies
Use recordAction() In a Table Widget
@awcodes okay, I added a view page for my invoices and checked that it is working. I then added
->recordAction(fn ($record) => InvoiceResource::getUrl('view', ['record' => $record]))
to my table which results in an Alpine Expression when I click the table row:
Alpine Expression Error: Unexpected token ':'
Expression: "$wire.http://sampleapp.test/projects/1/invoices/1('1')"19 replies
Refresh a modal after an extra footer action is performed?
Nevermind, I think I got the solution.
I had to define all actions at once within
extraModalFooterActions()
and then for each action define the display behaviour as a closure. for example with my "check" action:
->visible(fn (Invoice $record) => $record->status === InvoiceStatus::Booked)
This will cause the desired refresh behaviour of my modal footer.2 replies