[MAGNOLIA-8948] Request for making the response properties of endpoint delivery configurable Created: 13/Jun/23  Updated: 13/Jun/23

Status: Open
Project: Magnolia
Component/s: None
Affects Version/s: 6.2.31, 6.2.32, 6.2.33, 6.2.34, 6.2.35
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Liang Xin Assignee: Unassigned
Resolution: Unresolved 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   

Context

  • Some properties in the response from delivery api is not required, and it affects the client's program logic.
  • Remove those properties in the return json if those are not required.
  • Developer will be involved.
  • Make all response properties configurable in endpoint definition.

Use Cases

  • As a client within using delivery API, I would like to control that which node properties are not in the response, so that I can do not deal with many unused properties in the client program.

Current Status

  • I will need to customize a NodeWriter class to deal with this issue.

References, Proposals and Ideas

  • Can implement this like systemProperties in endpoint definition.

Designer Tasks

[To be filled by the Designer]

Delivery date

  • In next releases.

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