Closed lepikhinb closed 1 month ago
Same comment as in https://github.com/inertiajs/inertia-laravel/pull/634#issuecomment-2143360780.
Might be worth investigation if the PR https://github.com/inertiajs/inertia-laravel/pull/631 also solve this issue?
@VicGUTT it doesn't. However, I think #631 can be simplified a bit.
Alright, too bad. Thanks for confirming.
Sure, in what way? That PR simply reverted back the method "resolvePropertyInstances" to what it previously was
@reinink I rewrote the entire partial request resolving logic. It seems that the only way to support nested partial props without introducing any breaking changes is to check each prop independently to determine whether it should be included or excluded from the partial response.
Additionally, we need to resolve dot-notated props last to ensure they are merged after any parent closures are resolved.
Based on https://github.com/inertiajs/inertia-laravel/pull/634
This PR includes extra tests to ensure shared props can be included and excluded from partial responses.