[ECOMMERCE-582] Ecommerce Resolver for Delivery API Created: 05/Jul/23  Updated: 13/Sep/23

Status: Open
Project: E-commerce
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Mykola Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Sub-Tasks:
Key
Summary
Type
Status
Assignee
ECOMMERCE-583 Implementation Sub-task To Do  
ECOMMERCE-584 Review Sub-task To Do  
ECOMMERCE-585 Pre-Integration QA Sub-task To Do  
ECOMMERCE-586 QA Sub-task To Do  
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)
Epic Link: AuthorX improvements
Team: AuthorX

 Description   

Currently products are served from separate endpoint /.rest/ecommerce/v1/products
In headless approach and when choosing single product (teaser) it would be more performant if we return resolved product object with the page (the same way it works for content type resolvers)

something like this (similar to Focal resolver) would be nice

references:
  - name: productReference
    propertyName: product
    referenceResolver:
      class: info.magnolia.ecommerce.rest.ProductReferenceResolverDefinition
      implementationClass: info.magnolia.ecommerce.rest.ProductReferenceResolver 

maybe something similar for category also

Currently this is possible only through making request to pages, parsing product json and making second request to ecommerce so it takes relatively more time and resources


Generated at Mon Feb 12 01:45:27 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.