[MAGNOLIA-7100] New JCR nodebuilder API's addProperty operation doesn't accept Object Created: 31/Jul/17  Updated: 21/Aug/17  Resolved: 10/Aug/17

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: 5.5.6, 5.6

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

Issue Links:
Relates
relates to MAGNOLIA-5797 Align info.magnolia.jcr.nodebuilder.O... Open
causality
caused by MAGNOLIA-4183 jcr: JCR-based NodeBuilder Closed
dependency
is depended upon by MGNLUI-4252 Remove uses of the Content API 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: Basel 107, Basel 108, Basel 109
Story Points: 2

 Description   

With MAGNOLIA-4183 the Content API based node builder API was migrated to JCR. Unfortunately the addProperty operation (see info.magnolia.jcr.nodebuilder.Ops#addProperty) was migrated correctly, in fact breaking original functionality:

Previously it was possible to create any JCR property type, while with the new operation everything would be handled as String even though underlying logic remained the same.

We should open up the method signature form String to Object. This is binary compatible as it's a static class and we're widening the signature.


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