[MAGNOLIA-1303] Handle different property types in MgnlNode.setProperty Created: 16/Jan/07  Updated: 23/Jan/13  Resolved: 16/Jan/07

Status: Closed
Project: Magnolia
Component/s: core, workflow
Affects Version/s: 3.0.1
Fix Version/s: 3.0.2

Type: Bug Priority: Major
Reporter: Magnolia International Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-1304 Proper handling of PropertyType.NAME ... 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

 Description   

Currently only booleans and strings are supported: as a result, any other type of property is stored as a string and thus badly deserialized.



 Comments   
Comment by Magnolia International [ 16/Jan/07 ]

fixed in svn

Comment by Magnolia International [ 19/Jan/07 ]

also skipping properties with no name ("" or null)

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