!!! FEATURE: Separate properties and references in clientEval

[pKallert]

What I did
As discussed in neos/neos-development-collection#5156 references should be available separately in ClientEval

How I did it

I adjusted the logic for loading data for the right sidebar to be separated into properties and references.

depends on #3810

How to verify it

Use ClientEval:console.log(node) in the right to see that references are no longer in the properties array but now their separate item:

[grebaldi]

Nice one, thx @pKallert! 👍 by 👀

[mhsdesign]

Looks good sofar but ill have to try this out ;) It seems that with the transientValues we still mix properties and references but that seems sensible ^^

[mhsdesign]

i think i found a bug: the neos ui doesnt notice the deletion of a reference property. It will show up again after hitting apply.

this could be related to logic like this

neos-ui/packages/neos-ui-sagas/src/Changes/index.js

Lines 28 to 38 in 60262de

	// We immediately optimistically update node properties in state, before sending the persist request
	const propertyChanges = action.payload.changes
	.filter(change => change.type === 'Neos.Neos.Ui:Property')
	.map(change => ({
	subject: change.subject,
	propertyName: change.payload.propertyName,
	value: change.payload.value
	}));
	if (propertyChanges.length > 0) {
	yield put(actions.CR.Nodes.changeProperty(propertyChanges));
	}

or similar that relies on node.properties

[mhsdesign]

its a bit random that the source value is fetched here inside the component and not from the outside ... are there other places like this?