[MAGNOLIA-7217] Report any definitions that reference non-existing definitions Created: 06/Dec/17  Updated: 14/Feb/18  Resolved: 09/Jan/18

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: 5.6.2

Type: Improvement Priority: Neutral
Reporter: Antti Hietala Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by PAGES-152 Report any definitions that reference... Closed
Relates
relates to CONTEDIT-172 Report deprecated Template definitions Closed
causality
is causing MAGNOLIA-7262 TemplateDefinitionValidator produces ... Closed
relation
is related to MGNLDEMO-262 Wrong template availability in tourSp... 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)
Epic Link: YAML backwards compatibility
Sprint: Kromeriz 124, Kromeriz 125, Kromeriz 126, Kromeriz 128, Kromeriz 129
Story Points: 8

 Description   

Confirm that all problems with YAML definitions are reported to Definitions app

  • Definitions which reference definitions which do not exist.(For example a template definition references a non-existent dialog definition)

Reported messages should say

  • Which class / definition / whatever is deprecated / not found

Please note Magnolia's behaviour in those cases currently as a comment or in a wiki page.

Requirement in YAML backwards compatibility


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