-
-
Notifications
You must be signed in to change notification settings - Fork 118
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
Not compatible with Model::preventAccessingMissingAttributes()
#163
Comments
I have opened #165, but it seems like the tests locally pass, even when I test for both Do you have any snippet from which the problem comes off? |
I'll try to provide more information tomorrow. There might be Laravel Livewire involved. |
It seems to me that there is a problem with passing a whole model to a Livewire component (see: Passing parameters). However the error isn't invoked on the first rendering of a Livewire component, only after refreshing it. Should I open an issue in the Livewire repository? To be honest, I don't quite know what's going on under the hood and how the two libraries work together. |
@maciek-szn I can test against livewire. Do you have any mockup component i can start from? |
I've created a test repository. |
@maciek-szn I was able to fix it. After 16 days. 😬 |
Thanks a lot! |
Laravel 9.35 introduced
Model::preventAccessingMissingAttributes()
option (laravel/framework#44283). However this package isn't quite compatible with this mechanism, as it sometimes returns an error:The attribute [cacheTags] either does not exist or was not retrieved for model...
The text was updated successfully, but these errors were encountered: