[PAGES-922] LegacyPageWriter ignores page properties Created: 08/Nov/22  Updated: 23/Oct/23  Resolved: 15/Nov/22

Status: Closed
Project: Magnolia pages module
Component/s: None
Affects Version/s: 6.3.0
Fix Version/s: 6.3.0

Type: Bug Priority: Neutral
Reporter: Roman Kovařík Assignee: Canh Nguyen
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: 1.75d
Original Estimate: Not Specified

Issue Links:
dependency
depends upon PAGES-916 Create PageNodeTypeResolverDefinition... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[X]* Steps to reproduce, expected, and actual results filled
[X]* Affected version filled
Date of First Response:
Epic Link: DevX Bucket
Sprint: DevX 23
Story Points: 2
Team: DeveloperX

 Description   

Steps to reproduce

  1. Add custom field to a page dialog:
    form:
      properties:
        ...
        customField:
          $type: textField
    
  1. Add a page with this dialog
  2. Set a value to the text field
  3. Save.
  4. Request the page 
    http://localhost:8080/container/.rest/environments/main/delivery/pages/v1/sample-page?subid_token=...

Expected results

The value of the customField is returned in JSON response

Actual results

Page properties are ignored (areas and components are present). 

Workaround

Modify LegacyPageWriter.

Development notes

I'm not sure if LegacyPageWriter is a final impl as I was using a feature branch. Feel free to close the ticket and link an existing fix/replacement for this class.


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