major
minor
major
minor
minor
#27029
Failure to use PropertyInitializer for list-valued properties.
If a tl:PropertyInitializer is configured for a property, it is used to pre-populate the field value in the declarative form.
If a `tl:ConfigurationItem` containing such a property is created within a list, this initializer is not applied.
Code Migration
This fixes the bug that caused `GenericFunction` s used in derived properties to not be set to `null` for "Mandatory" properties in the path that were not set. `GenericFunction`s must handle this. See also the migration in #18097:
Implementations of ` GenericFunction ` used in derived properties must be able to handle ` null ` as a value for each of their parameters.
* These can be found, for example, by opening the call hierarchy for `Derived.fun()` in Eclipse.
* Theoretically, it is sufficient to consider only those derived properties that refer to mandatory properties, or to other derived properties that refer to mandatory properties. However, since the type of the property can change in derivations of the interface, this is difficult to keep track of and can lead to errors in the event of future changes or extensions to the type hierarchy. Therefore, the functions of all derived properties should be adjusted accordingly.
Test
TestDeclarativeForms.script.xml