[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: |
|
||||||||||||||||
| 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. |