-
-
Notifications
You must be signed in to change notification settings - Fork 38
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: magic methods on component not being called #151
base: main
Are you sure you want to change the base?
Conversation
Is this also the way Livewire V2 does it to avoid this be a breaking change as soon as I release Magewire V3? |
It's really confusing that this doesn't work. The docs mention
I also don't see a reason why it shouldn't work in this case. In which cases are the hooks called, then? I really think this should be picked up. |
Hi Simon, Thank you for your response. As mentioned to @adamzero1, we first need to verify if this works the same way in Livewire. Additionally, the documentation you're referencing is written by Hyvä, and I am unsure if it was thoroughly tested before publication. Could you please test this yourself to confirm? This will allow me to proceed with merging and releasing it. In the meanwhile you can replace Thanks! |
I cannot test this in Livewire myself at the moment, I'm afraid. Either I don't understand your workaround or it doesn't work... In both versions, the hook method
(plus, having implemented a
Am I missing something? 👀 |
Why do you want a hook method to act when you have your own Reason why is that I'm trying to stick as close as possible to Livewire for now to avoid big bic when wanting to migrate to Magewire V3 in the future. There is an option we part ways with having everything identical, but that decision will be made after releasing V3. So for now you should be able to proceed and leave those "magic" methods behind. Please feel free to DM me on Discord or Slack if you have any related questions regarding this topic. |
The documented magic methods don't appear to work for "standard" components.
The logic described in the docs (calling updated / updatedPROP) only seems to be implemented for the SyncInput action.
Should now be in place for the set method also.