[MAGNOLIA-4038] PropertyValuesTask#checkAndModifyPartOfPropertyValue should behave similar to other check-methods Created: 12/Mar/12 Updated: 23/Mar/12 Resolved: 20/Mar/12 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | None |
| Fix Version/s: | 4.5.2 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Daniel Lipp | Assignee: | Milan Divilek |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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)
|
| Description |
|
In contrast to the other check-methods in PropertyValuesTask, checkAndModifyPartOfPropertyValue will throw a RepositoryException in case the property is not existing. This should be aligned. |
| Comments |
| Comment by Daniel Lipp [ 16/Mar/12 ] |
|
Please add test as well. |