Not expected behavior of $component/$parent helper about alpine-magic-helpers HOT 5 CLOSED

Hi @leobm

Thanks for this report. I'll set up a demo and try it out. There's likely going to be some edge cases that need to be worked out, or that might just not work. Good to figure them out though.

Any difference if you use $component()? That works slightly different behind the scenes.

I might not get back to you until tomorrow though.

from alpine-magic-helpers.

I put your code here with the source code https://codepen.io/KevinBatdorf/pen/8dd61ec92f00eb90ba48eee6bc6b8665?editors=1010

from alpine-magic-helpers.

Okay, I figured out the bug. It's related to $el.parentNode.closest('[x-data]') which isn't super reliable to find the parent in hindsight.

Here's a clear example of the bug where you can see it reaching for the wrong component:

https://codepen.io/KevinBatdorf/pen/0b3e58b7f8d6bd1d18b1d6e8e424c908?editors=1010

It's late where I am now though so it won't be until tomorrow before I can implement a fix, so for now I'd suggest switching to $component(), unless you were just testing it out :)

Thank you again though, and I'll update here when I have more info.

from alpine-magic-helpers.

Hi, Have a fix if you want to test it out. Will merge it in later

https://codepen.io/KevinBatdorf/pen/b9d3e9746f1156495415f5306b5059bd?editors=1000

from alpine-magic-helpers.

Fixed in 0.3.1

Feel free to open the issue if still experiencing issue. Thanks again for the issue

from alpine-magic-helpers.