[MGNLREST-89] Empty arrays coming through as null in JSON Created: 11/May/17  Updated: 24/Mar/22  Resolved: 24/Mar/22

Status: Closed
Project: Magnolia REST Framework
Component/s: None
Affects Version/s: 1.2.1
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Nickolaus Wing Assignee: Unassigned
Resolution: Outdated Votes: 0
Labels: apiteam
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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

Related to MGNLREST-83, another change we noticed after the latest updates is that nodes with no children come through with

{ nodes: null }

instead of

{ nodes: [] }

. This is a change from the previous behavior and can break code that assumes an array in all cases.



 Comments   
Comment by Christopher Zimmermann [ 24/Mar/22 ]

Endpoint now does return empty array instead of null. Closing as outdated.

Generated at Mon Feb 12 06:56:29 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.