[MAGNOLIA-5182] CheckAndModifyPropertyValueTask should allow more than one expected value Created: 12/Jul/13  Updated: 18/Dec/13  Resolved: 02/Aug/13

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: 4.5.10, 5.0.2, 5.1

Type: Improvement Priority: Neutral
Reporter: Milan Divilek Assignee: Milan Divilek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
is causing MAGNOLIA-5524 CheckAndModifyPropertyValueTask throw... Closed
is causing MGNLRES-64 Relative path in CheckAndModifyProper... Closed
is causing MGNLRSSAGG-92 Fix RSSModuleFeedGeneratorTest 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)
Date of First Response:

 Description   

CheckAndModifyPropertyValueTask has attribute expectedCurrentValue which is type of String. It would be great to allow more than one expected value.



 Comments   
Comment by Roman Kovařík [ 01/Aug/13 ]

Have to be backward compatible...both relative and absolute path should be supported.
-> update task to Resources 1.5.4 is failing, see MGNLRES-64.

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