Dynamic tooltip text? about alpine-tooltip

[ryangjchandler]

Hi @nijlandvpr I'll look at adding support for this. I think it should just be a case of setting the text for the tooltip when it's toggled.

[ryangjchandler]

@nijlandvpr Can you see the x-data property changing in the inspector? Outside of a Livewire environment, changing the value of the property correctly updates the tooltip value.

I am able to reproduce the problem inside of a Livewire component. The x-data does update in the DOM, so I'm actually going to guess that this is a problem with how Livewire & Alpine are working together, i.e. Alpine isn't correctly re-initialising the component when the DOM is patched by Livewire.

Even without the tooltip library, a simple x-text="tooltip" doesn't update either.

[nijlandvpr]

@ryangjchandler Thanks for taking the time on this. Yes, my scenario is inside a Liverwire component the x-data updates but the tooltip remains as it was when the page first loads.

[ryangjchandler]

@nijlandvpr Yeah, I don't think this is a problem with the package. I'd recommend opening an issue / discussion on the Alpine or Livewire repo.

[nijlandvpr]

@ryangjchandler Sure thing - I thought I'd start with the expert on the package. I'm also experiencing other issues with Livewire where some actions return a 404 to a "messages" route while others don't. Looks like it's losing how it recognizes DOM elements and substituting with a default - something like that anyway. New tech === "keep it simple stupid" is the message!

Thanks

[rcubitto]

I encountered the same problem, I was able to solve it using @entangle and an extra property in the Livewire component (where you should store "Enable" or "Disable")

[nijlandvpr]

@rcubitto Are you saying you use @entangle to change the text of the tooltip?

x-data={ tooltip: @entangle('someStringProp') }

[rcubitto]

@nijlandvpr yes, if the value of someStringProp changes, the tooltip gets updated accordingly.

[nijlandvpr]

@nijlandvpr yes, if the value of someStringProp changes, the tooltip gets updated accordingly.

The scenario I was looking at involved a backend rendered table, with rows containing a boolean is_disabled state. Even if is_disabled was text, looping through the rows as objects or array elements wouldn't entangle - I think!

x-data={ @entangle('user->is_disabled') }

[ryangjchandler]

I'm going to close this issue for now since it's not a problem with the package, more of an Alpine/Livewire interop/compatibility thing.

If anybody comes here later looking for the same thing -- you can either use @entangle / $wire to keep the prop in sync, or use a method on the Livewire component that returns the value, then inside of x-tooltip do something like $wire.myMethod()