-
Notifications
You must be signed in to change notification settings - Fork 1
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
does not support sub paths #2
Comments
How would this be used/defined in CB? If it's aways an field pointing to an entity / array of entities it may not be the responsibility of the databag here. Maybe the object itself should use an sub-object/objectCollection instead. Like we do with address, phoneNumber and so. |
Examples: Known Or may want to define a php-entity like this: MyDebtorEntity::getStreet();
// returns for example debtor.addressReference.address.street via the DataBag solution
// without having to define a load of misc php-entities The main reason is that it is not a proper databag as you can not set/get more than two sub paths, and has unexpected behaviour due to this. |
When using with sub paths it fails;
i.e.
one.two.three
will always return the default value even if it is set:And also when setting it sets unexpected data:
The above
$state
returnsWhere
two
is not the expected object containingthree
with thevalue
but an array just containing thevalue
.The text was updated successfully, but these errors were encountered: