#24908 Double (ugly) error messages german/english in Expert search

enhancement

major

#24864

Create TLEnumeration in module tree

#25147

Provide layout for model-based search in base

minor

#24403

Rewriter to remove old data from DOStorage during migration

#24948

Upgrade ACE Editor to version 1.4.10

#25096

Comparator for Named

#25103

Change OptionProvider to OptionModel

#25112

Common superclass for TLAnnotation with string value

#25124

Display of the sorting in the list administration

#25129

Configure model filter on ModelService

#25131

Moving various ResourceProviders from element to tl

#25155

Name mapping for Named

#25159

Remove ModelSpec.Null as option for the model

#25170

Clear and uniform display of error messages

defect

major

#25095

Error when configuring views in-app

#25117

Log ERROR because of license in newly installed application

#25118

Invalid component reference in meetingDialog

#25121

New application: BoxLayoutTag$ConfigService module not started

minor

#24851

DefaultFormFieldControlProvider always hard sets the ButtonRenderer

#24870

Attributes tab in Model Editor also visible for modules

#24886

Wrong disabled icon for detail dialog opener in sidebar theme

#24907

Incorrect "matching parentesis" markup in TL script editor

#24908

Double (ugly) error messages german/english in Expert search

#24911

Context help in TL script editor not case-insensitive

#24955

Invisible icons / texts in Dezenzt theme

#25092

I18N In-app development issues

#25093

Usability problems with in-app development

#25114

Form editor does not adapt to the theme?

#25115

Design mode button no longer red after tab addition

#25119

404 Error "favicon.ico"

#25120

Dependency problem in new application

#25128

Errors in the log when starting a new application

#25148

Missing translation "is empty" "is not empty"

#25154

Missing serialization of configuration properties in DisplayStrategy.IGNORE

#25158

Remove own component as option for model source

#25161

Target Label requires MainLayout when loading configuration

#25168

Delete unused FormEditorApplyHandler

#25169

TL script: CCE when comparing integer and double

#25172

Repair surface defects

#25176

Model editor not enabled by default in new app

#25178

Error icon overlaps dialog opener in grids in decent theme

#25187

Forms in dialogs predominantly non-reactive

nice-to-have

#25181

Search icon in decent theme not centered when selected

defect (User-visible)

minor

#24908

Double (ugly) error messages german/english in Expert search

If you enter an invalid TLScript expression in the model-based search, you will receive duplicate error messages that mix languages (if the application language is German). This is undesirable.

In general, this problem occurs for every application language except English. When parsing an invalid TLScript expression, a `tl:ParseException` is thrown. The `ParseException` is then handled in `ExprFormat#handleParseException ` and wrapped in a `tl:ConfigurationException`. ConfigurationException is a tl:I18NException, meaning it is internationalizable. The tl:ResKey of the ConfigurationException is parameterized in the resources and is populated with the English-language error message from the ParseException.

As a result, a user with German set as the application language will see an error message on the interface that is a mix of German and English.

Implementation

If the TLScript expression is found to be invalid during parsing, this warning is displayed:

Test

Open the model-based search and enter, for example,

`DemoTypes`.get

in Expert Mode and view the results. The warning message described above should appear.