-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Closed
Labels
P3: NormalPriority mark - normal priorityPriority mark - normal priorityfeature requestRequests for new features. Please be as specific as possible and provide proposal API if it you canRequests for new features. Please be as specific as possible and provide proposal API if it you can
Milestone
Description
What is the motivation for adding / enhancing this feature?
In 1.12 (develop) there is added new action for fetching category/product/cms_page by url_path - mapFallbackUrl. It makes request with one query that points to multiple entities. In this task we need to find a way how to cache product data in saveFallbackData. We need to handle all types of products (simple, configurable, bundle_options, custom_options, group). After reaching this goal, we will not have to make an extra request when product page is loaded.
What are the acceptance criteria
- - works for all type of products
- - after reaching product page we don't have additional request for product data
Can you complete this feature request by yourself?
- YES
- NO
Which Release Cycle state this refers to? Info for developer.
Pick one option.
- This is a normal feature request. This should be available on https://test.storefrontcloud.io and then after tests this can be added to next Vue Storefront version. In this case Developer should create branch from
developbranch and create Pull Request2. Feature / Improvementback todevelop. - (Pick this option only if you're sure) This is an important improvement request for current Release Candidate version on https://next.storefrontcloud.io and should be placed in next RC version. In this case Developer should create branch from
releasebranch and create Pull Request3. Stabilisation fixback torelease. - (Pick this option only if you're sure) This is a critical improvement request for current Stable version on https://demo.storefrontcloud.io and should be placed in next stable version. In this case Developer should create branch from
hotfixormasterbranch and create Pull Request4. Hotfixback tohotfix.
Additional information
Perfect solution would be without breaking changes.
Metadata
Metadata
Assignees
Labels
P3: NormalPriority mark - normal priorityPriority mark - normal priorityfeature requestRequests for new features. Please be as specific as possible and provide proposal API if it you canRequests for new features. Please be as specific as possible and provide proposal API if it you can