[PAGES-225] Let the DialogAwareTemplateDefinitionValidator use the non-deprecated dialog registries to avoid false positives Created: 08/Jan/20  Updated: 16/Mar/20  Resolved: 12/Mar/20

Status: Closed
Project: Magnolia pages module
Component/s: None
Affects Version/s: None
Fix Version/s: 6.2

Type: Bug Priority: Neutral
Reporter: Chuong Doan Huy Assignee: Aleksandr Pchelintcev
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screen Shot 2020-01-08 at 1.08.34 PM.png    
Issue Links:
Problem/Incident
causes MKTAUT-90 Edit form dialog show as invalid in P... 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
Sprint: UI Framework 16, UI Framework 18, UI Framework 19
Story Points: 1

 Description   

When component dialog using new ui-framework, the definition app report problem as "Dialog xxx is not registered" with MAJOR severity. But the component dialog works perfectly.

Current investigation shows that DialogAwareTemplateDefinitionValidator is still using the old "info.magnolia.ui.dialog.registry.DialogDefinitionRegistry" which may cause the problem.

 


Generated at Mon Feb 12 06:16:51 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.