[MAGNOLIA-8121] Improve YamlDependencyResolver interface and implementation Created: 24/Jun/21  Updated: 08/Jul/21  Resolved: 02/Jul/21

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

Type: Task Priority: Neutral
Reporter: Aleksandr Pchelintcev Assignee: Rishab Dhar
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Issue split
split from MAGNOLIA-8060 Resolve definitions from light module... Closed
split from MAGNOLIA-8099 Refactor code duplication introduced ... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Epic Link: SaaS project configuration
Sprint: Cloud Service 12
Story Points: 2

 Description   
  • the interface name YamlDepResolver doesn’t properly explain the API behaviour (it’s the content that it resolved)
  • the method that resolves content also under the hood registers the dependency as a side effect

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