Enhancement
Major
Detail
Bugfix
Detail
#26484
In-app template for grid and tables: Function "Verifier for use as list item" does not get component model
#26885
Constraints on declarative forms with arguments from a container reference lead to errors for new elements
#26922
With generated subject classes, a default provider of an attribute in a non-structure class does not get a create context
Bugfix
Detail
#26529
Model transfer to development environment: ResKeys remain in dynamic properties
During model transfer to the development environment, dynamic ResKeys are transferred to the module-specific translation tables (e.g. attribute names), but are not yet removed from the dynamic translation tables afterwards.
However, this should take place in order to distinguish static and dyn. translations.
Code migration
In application configurations, the <static-bundles> tag around the resource bundle definition must be removed:
From
#!xml <config service-class="com.top_logic.basic.util.ResourcesModule"> <instance class="com.top_logic.util.resource.analyzer.IDEResources"> <static-bundles> <bundles> <bundle name="test.polymorphismMessages"/> </bundles> </static-bundles> </instance> </config>
make
#!xml <config service-class="com.top_logic.basic.util.ResourcesModule"> <instance class="com.top_logic.util.resource.analyzer.IDEResources"> <bundles> <bundle name="test.polymorphismMessages"/> </bundles> </instance> </config>
Test
- In-app create new module with custom translation.
- Log-out/login-in and check that translations are still there.
- Reboot and check that translations are still there.
- Transfer module to development environment.
- Check that translations are still there.
- Shut-down, change the module and change the exported translation in the files.
- Start-up and check that changes have been applied.