Fix/apply-texture-prop

[roelkok]

Currenty if a texture prop changes, the new texture gets copied into the previous one. This is incorrect, since the original texture might also be used elsewhere or be used later on.

The proposed fix is to check whether the target has an UUID. If that's the case, we assume it's an object we don't copy new values into with a prop change.

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit c8ecb44:

Sandbox	Source
example	Configuration

[drcmda]

we're discussing atm. i think uuid check is a little sketchy, we don't know which and how many classes this would affect. it could create quite unreliable behaviour.

there might be a solution in sight. my current instinct is to check if the prop used to be null originally which indicates a non-read-only non-default prop, which should later be assigned, not copied.

for the moment please either key={...} your material or useMemo-clone the texture, this should solve it temporarily. v9 will then have a fix.

[drcmda]

fix c89e20a