-
-
Notifications
You must be signed in to change notification settings - Fork 222
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BUG: Cannot unset defaultValue
via CreateNodeAggregateWithNode::$initialPropertyValues
#5154
Comments
nvm deleted my previous comment I thought unsetsValueWithDefault is a feature here^^ Still seems right behavior? |
Hmmm i dont think its right if a followup |
Wait what? I don't think you should be able to unset default values, you can overwrite them with other values but not remove them? |
😂 hahah yes sounds legit ... i just wondered a year ago what the behaviour might be and observed that its possible and put it in stone via the node template tests :D |
While the change #4322 improved the unset handling of properties a lot, it introduced a regression.
Using the following NodeType
and creating it but using
would originally set
unsetValueWithDefault
toNULL
in the database. This was the behaviour in Neos 8.3 and Neos 9 before the mentioned change. Now when fetching the nodes properties we get the following result - the default value is still present:The reason for that is that we filter out the unsets when creating a node (under the impression that no one would do this ^^):
neos-development-collection/Neos.ContentRepository.Core/Classes/Feature/NodeCreation/NodeCreation.php
Line 88 in 7db53b6
A workaround for now is to followup with a
SetNodeProperties
commandThe text was updated successfully, but these errors were encountered: