[Calculated value] Context for localized calculated field in object brick

[BlackbitNeueMedien]

When you have a localized calculated field in an object brick there is a conflict with the context. As https://pimcore.com/docs/6.x/Development_Documentation/Objects/Object_Classes/Data_Types/Calculated_Value_Type.html states about context:

• Localized fields:
  • position | the language ("en", "de", ...)
  • ownerType | "localizedfield"
  • ownerName | the name of the localized field ("localizedfields")
• Objectbricks
  • ownerType | "objectbrick"
  • ownerName | the name of the objectbrick field inside the object
  • fieldName | the name of the attribute inside the brick
  • index | the name of the brick
  • keyDefinition | the calculated-value field definition

For object bricks also field position gets set but to the same value as fieldName:

pimcore/models/DataObject/ClassDefinition/Data/Objectbricks.php

Lines 179 to 180 in 22882be

	$fieldData = new DataObject\Data\CalculatedValue($fd->getName());
	$fieldData->setContextualData('objectbrick', $this->getName(), $allowedBrickType, $fd->getName(), null, null, $fd);

When you want to determine the language for the value generation of the calculated field, we need to set position to the language here. This currently does not work because the object brick fetches all descendant calculated value fields, not only children - bypassing the localized value field which would add the language as field position:

pimcore/models/DataObject/ClassDefinition/Data/Objectbricks.php

Line 175 in 22882be

self::collectCalculatedValueItems($collectionDef->getFieldDefinitions(), $calculatedChilds);

[weisswurstkanone]

what would be your proposed solution? mayne we can add an additional value?