Danie Ramdhani
Danie Ramdhani
it still leaks after element is removed from DOM and will make `Uncaught (in promise) Could not find Livewire component in DOM tree` if you use `$wire` inside `$wire.$on` and...
related: https://github.com/laravel/framework/issues/50994 and i think it won't fix. try: ```blade content ```
Interestingly, when i change the language (and navigate to same url with same query string) then showing/hiding columns, it throw type error from columns props. https://github.com/user-attachments/assets/e96321e0-d6c3-4af1-8f9a-9c2a8026a9a7 can i disable the...
> ``` > $this->setQueryStringForColumnSelectDisabled(); > ``` Um, it didn't work. it still add the query string.
> Hmm, did you do that on a fresh table, with that in configure? > > Can you try adding this to your configure as well to test > >...
> Not sure yet whether I'll remove the setQueryString or repurpose it. I mean, query string came from public properties right? Like i've never use setQueryString before. > Effectively, the...
like i said before it would be good case for view that is reusable. i..e. i have preview post content (its not reusable, only for posts table). https://github.com/user-attachments/assets/af271745-eb38-45b9-a476-a28b8ead91b8
livewire is using alpine js for binding data, so i think it's not related to livewire (see: https://github.com/alpinejs/alpine/discussions/4018). i think, you can close this PR.
can you give me the discussion link?
mmm... yeah this kinda complicated because livewire v3 is using alpine js for binding the data 😅... (because this is the bug in alpine js itself)