Laravel Model 'strict modes' cause all pages to fail to load (at least Resource, Lens)

[juse-less]

• Laravel Version: 9.35.1
• Nova Version: 4.16.1
• PHP Version: 8.1.11
• Database Driver & Version: Percona/MySQL 8.0.29-21
• Operating System and Version: AlmaLinux 8.6
• Browser type and version: Arc 0.72.0 (35182) / Chromium 106.0.5249.119
• Reproduction Repository: https://github.com/juse-less/laravel-nova-issues/tree/issue/laravel-model-strictness

Description:

Apologies in advance. I'm not sure if this should be considered a bug, or a feature request to use that Laravel feature.

When using Laravel's newer Model::shouldBeStrict(), pages fail to load as Laravel is throwing exceptions.
More specifically it appears to be Model::preventAccessingMissingAttributes() that is throwing a fit.

The error thrown is

The attribute [pivot] either does not exist or was not retrieved for model [<Model FQN>].

The Model in question (User), in the provided repo, has no relationships.

Attached video and screenshot of the issue

ScreenShot.2022-10-14.at.22.27.26.mp4

Detailed steps to reproduce the issue on a fresh Nova installation:

1. Check out the repo provided, using the branch issue/laravel-model-strictness
2. Install dependencies, and publish assets
3. Create a user
4. Log in to Nova
5. View any page (like the users resource)

[crynobone]

After various tests/changes to Nova, it seems impossible to support Model::preventAccessingMissingAttributes() without introducing breaking changes. As a result, I have submitted laravel/framework#44627 where you should be able to disable strict mode when accessed in Nova.

[juse-less]

I had a hunch that was the case. In the meantime I've enabled all 3 separately, with Model::preventAccessingMissingAttributes() checking for the Nova routes as well. 👍

Thank you for putting time into this. 🙂

[crynobone]

In the next release, Nova will automatically toggle Model::preventAccessingMissingAttributes() when handling Nova Requests.

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.