[MGNLREST-308] Expose JcrDeliveryEndpointDefinition via provider, refactor node wrapping Created: 18/May/21  Updated: 29/Jun/21  Resolved: 04/Jun/21

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

Type: Task Priority: Neutral
Reporter: Robert Šiška Assignee: Jaroslav Simak
Resolution: Fixed Votes: 0
Labels: VN-Testing
Remaining Estimate: Not Specified
Time Spent: 0.25d
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MGNLPN-474 Get (stateless) personalized content ... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Epic Link: Headless p13n
Sprint: HL & LD 29, HL & LD 30, HL & LD 31
Story Points: 3

 Description   

In preparations for personalization over REST, we need to refactor JcrDeliveryEndpoint a little bit.

We need to:

  • Expose JcrDeliveryEndpointDefinition so that request/response filters may access it and act accordingly on the setup configured on the definition level
  • Set priority for request/response filters - especially needed for setting priority
    • priority will ensure node wrappers are applied in order we need
  • Refactor (and deprecate) ReferenceContext to be part of the more global one, which will also carry the endpoint definition

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