[MAGNOLIA-6928] TypeResolvers do not report any problems making it hard to identify issues with definitions Created: 20/Jan/17  Updated: 23/Jan/17

Status: Accepted
Project: Magnolia
Component/s: None
Affects Version/s: 5.5.2
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Philip Mundt Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File unknown_class.txt     Text File unknown_fieldType.txt    
Issue Links:
Relates
relates to MAGNOLIA-6901 Generalise bean type resolution strat... Closed
relates to MGNLUI-3882 Reference fields by name as well as b... Closed
duplicate
is duplicated by MAGNOLIA-6912 Handle transformer warnings for custo... 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)

 Description   

When specifying a class (see info.magnolia.transformer.ClassPropertyBasedTypeResolver) or fieldType (see info.magnolia.ui.form.fieldtype.resolver.FieldTypeResolver) in any definition or dialog definition respectively that does not resolve or has an invalid value, NO problem is reported.

The only hint one gets are exceptions in the case of unknown values (empty values do not show up at all) see attachments.


Generated at Mon Feb 12 04:19:09 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.