-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Builder bug with addActionBetween #12825
Labels
Milestone
Comments
This is a really interesting bug, and it seems to occur in Livewire itself when you change the order of keys in an existing array. Screencast.2024-06-03.10.31.50.mp4I'm not sure if this is a valid solution for the bug, but it provides some additional information. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Package
filament/filament
Package Version
v3.2.40
Laravel Version
v11.7.0
Livewire Version
v3.4.12
PHP Version
PHP 8.2.8
Problem description
When adding items with the addBetweenAction once there are 4-5 items in the state the last item looses its alpine data somehow resulting in alpine throwing up in the console because ‘isCollapsed’ is undefined.
But then it reinitializes itself. But continues to not have the alpine data set on any following actions.
So if you click on collapse all they all collapse except that one. But the bug still happens regardless of collapsible or not.
addAction doesn’t seem to trigger the issue, probably because the new item is always at the end of the state array.
Expected behavior
Blocks do not loose their alpine x-data properties.
Steps to reproduce
Screen.Recording.2024-05-16.at.8.47.17.AM.mov
Reproduction repository
https://github.com/awcodes/builder-bug
Relevant log output
Donate 💰 to fund this issue
The text was updated successfully, but these errors were encountered: