[CFGUI-182] [SAAS] - Definitions app should show problem when dialog field $type is wrong Created: 27/Jul/23  Updated: 27/Jul/23

Status: Open
Project: Definitions App
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Christopher Zimmermann Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
clones MAGNOLIA-9031 [DX-core] Definitions app should show... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Release notes required:
Yes
Epic Link: DevX Bucket
Team: DeveloperX
Work Started:

 Description   

This ticket is for SaaS, CFGUI-181 is for DX-Core.

When developer specifies a field $type that does not exist, a useful warning is displayed in the logs, but no "problem" is displayed in the "Definitions app". A problem should be displayed otherwise it is difficult for a developer to find the cause of the problem. 

The same problem happens on DXCORE and SaaS, but the problem is slightly worse on SaaS as the logs cannot be seen by the developer and the "Configuration Monitor" does not report any problem.

 

To reproduce:

Note that "textArea" is not a valid $type here.

Use the following dialog for a page template: 

 

label: My Page
form:
  properties:
    title:
      label: Title
      $type: textField
      i18n: true
    text2:
      label: Test
      $type: textArea
      i18n: true

 

 

Then create a page of that type and try to edit that page in the page editor. 

> You get an exception that the page cannot be edited.

Go to the Definitions App - notice that there are no problems shown in the Definitions or Problems tab for the incorrect dialog.

Here is the useful warning message in the logs on DXCORE

2023-06-23 11:38:09,763 WARN  a.config.resolver.AnnotationProcessingTypeResolver: Encountered the '$type' property but failed to resolved the type from its value: [textArea]. Available types: [jcrMultiField,radioButtonGroupField,pageLinkField,staticField,textField,comboBoxField,twinColSelectField,checkBoxField,multiField,switchableField,checkBoxGroupField,jcrMultiLinkField,passwordField,compositeField,listSelectField,richTextField,codeField,resourceLinkField,tokenField,linkField,dateField,uploadField,sliderField,jcrMultiValueField,damLinkField,hiddenField] 

 


Generated at Mon Feb 12 00:45:49 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.