enhancement
critical
major
minor
minor
#25907
Layout editor: inconsistent behavior of unfold state, selection and reaction to object creation
#25951
Application tests: CheckLabeledExecutabilityOp fails to assert non-executability of literal ResKey reasons.
#25952
Model Editor: Enum default provider does not work for enum references for which singleton link storage was explicitly selected
#26002
ConfigurationItem-valued properties with format annotations may cause an attempt to create abstract config items when deserializing null values
#26012
Help editor crashes when a user has chosen a language that is not in the supported languages of the application
#26039
Gridcomponent: Display of context menu for new (transient) row object leads to UnsupportedOperationException
#26085
An attribute of type tl.model.search:Expr is not displayed in the form above a TL script editor
#26111
Context menu commands for table rows are erroneously executed on the table model when opening the context menu in the background of the table
#26153
Migration: Replay fails if string values with line breaks are contained in the dataset where a line ends with a semicolon
#26171
A TL script expression entered in a wizard template is reformatted when transferred to the final template
#26223
TL script: Under unfavorable conditions wrong parameter values when evaluating local functions
defect
nice-to-have
#26089
Template for new app: Default module is not loaded via Autoconf
Currently, the default module for a new app is added to the application configuration. If you edit this module within the app and re-export it to the development environment, it is included twice (once via AutoConf and once via the application configuration). Essentially, this has no negative effects because duplicate references to configuration files are ignored when the configuration is read.
Improvement
- Include the module from the template in the same way it would have been included if the module had been created directly in the application.
Test
- Create a new application.
- Start the application. Create a type in the application’s module using the in-app method.
- Import the module into the development environment.
- Verify that the application module was integrated only once.