[MAGNOLIA-7673] HasPropertyDelegateTask should always interpret parentPath as an absolute path Created: 01/Nov/19  Updated: 01/Nov/19  Resolved: 01/Nov/19

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

Type: Bug Priority: Neutral
Reporter: Michael Duerig Assignee: Michael Duerig
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by PAGES-204 Remove usages of deprecated Content A... 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
Epic Link: Remove Content API
Sprint: Release 6.1.3 & Content API RM
Story Points: 2

 Description   

HasPropertyDelegateTask fails when passing a relative path to parentPath. Its predecessor (PropertyExistsDelegateTask) would just interpret the path as relative from root (and thus absolute).

This slight difference in behaviour causes PagesModuleVersionHandlerTest#testUpdateFrom54InstallsContentConnector of the pages app to fail.


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