Closed RobertBoes closed 1 month ago
Hey @RobertBoes, without looking to deep into it and although that was not the intended fix of my PR, I was wondering if my PR #631 doesn't also resolve the issue described here?
The point of my PR was to simply revert back the order of which property instances and arrayable properties were resolved prior to #620.
I think #620 introduced a breaking change when sharing props through the middleware, as described in #633
A use-case would be the following:
Then render the page using:
This would result in just
props: { user: { name: 'John' }}
being sent to the frontend instead ofprops: { user: { name: 'John', verified: true }}
, with this PR the latter would happen.I attempted to fix the issue by merging the props instead of overwriting them. However, I'm not actually sure why this feature worked before, since it seems like props were always overwritten.