Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Remove x-ignore around nested Alpine components #15062

Merged
merged 1 commit into from
Dec 11, 2024

Conversation

danharrin
Copy link
Member

The Async Alpine (v1) version was locked a while ago due to issues released in a minor version. We cannot receive updates to this package.

2 weeks ago we locked Livewire in v3.2.125 as it caused issues when using tables.

A discussion revealed the reason the tables broke was because Alpine.js started not initialising components within x-ignored elements.

The x-ignore needs to be present when using Async Alpine v1, and our tables use Async Alpine and contain nested Alpine.js components.

Since it does not look like this change is going to be reverted in Alpine.js, and it is not great having the Livewire version locked in Filament as it prevents users from being able to use new Livewire features elsewhere in their apps, I am removing Async Alpine from the tables so I can remove the x-ignore and unlock Livewire.

@danharrin danharrin added the bug Something isn't working label Dec 11, 2024
@danharrin danharrin added this to the v3 milestone Dec 11, 2024
@danharrin danharrin merged commit 7611127 into 3.x Dec 11, 2024
21 checks passed
@danharrin danharrin deleted the nested-components-within-x-ignore branch December 11, 2024 13:00
danharrin added a commit that referenced this pull request Dec 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

1 participant