Store API Cleanup #3169
Replies: 3 comments
|
Since Shopware 6 has an API first approach, IMHO you should concentrate to improve the full page caching support. For example in https://github.com/shopware/platform/blob/trunk/src/Core/Content/Product/SalesChannel/Listing/ProductListingRoute.php#L88 by supporting more GET requests you can make use of the internal full page cache. If this is not possible, there is a way to convince the FPC with a bit of trickery to cache even POST/Search requests. The benefit would be high: Having only a minimal bootstrapping for store-api requests would greatly improve loading time. Especially if you need to access multiple endpoints on the first time (loading menu, products, manufacturers, ... on first visit) |
|
Will be part of the HTTP Cache rework and in some kind of the read optimized storages (#3165) |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Effort: low
Description
Some store API routes returns the entity collection instead of the entity search result. This does not allow to use aggregations.
Benefits
Break strategy
We change the API Response of following routes to an entity search result
All reactions