major
minor
major
minor
#26382
Error messages "Duplicate tag name..." when starting an application in the IDE from a TL-Studio
#26405
TTypeRewriter logs warning "Unable to resolve items by external reference" also unnecessarily
#26431
Changed superclass relationship leads to changed attribute list in the form editor only after a restart
#26484
In-app template for grid and tables: Function "Verifier for use as list item" does not get component model
#26536
When rendering HTML from TLScript expressions, configured renderers are not taken into account
#26797
Transaction with user input: invisible properties of the form model cannot be assigned values (initialized)
#26885
Constraints on declarative forms with arguments from a container reference lead to errors for new elements
#26921
ClassCastException when evaluating security rules that refer to (non-structuredElement) singletons of a module.
#26922
With generated subject classes, a default provider of an attribute in a non-structure class does not get a create context
#26988
In-app documentation generator does not extract documentation for overwritten config properties
#27027
Declarative forms: SelectField disappears after upload if option list depends on mandatory property
#27042
MaintenanceJspBase should write to the log first, then to the client, instead of the other way around.
enhancement
For example, if types in the model cannot be resolved, the rest of the model resolution process is aborted, but this does not prevent the application from starting. The application then fails when committing the new model, displaying a completely inexplicable error message.
Either you must try to “fix” the error in the model file as best as possible and start the application anyway (which would be useful if the error was built into the app, assuming that’s possible), or you must cancel the application launch with the correct error report.
Test
- Model with a reference to an unknown type.
- Start the application.
- Expected behavior: The launch aborts with exactly this error.