fix: Remove x-ignore around nested Alpine components #15062
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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-ignore
d 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.