feature/2167

[pkarw]

Related PR: https://github.com/DivanteLtd/vue-storefront/pull/3962/files

I've moved the ElasticSearch query construction to the api. There is an additional parameter request_format; when search-query the Elastic query is constructed server-side - on the API level.

I've moved the Query Builder to separate repository: https://github.com/DivanteLtd/storefront-query-builder which is now shared with vue-storefront and will be shared with storefront-api projects.

This is Work in Progress and not ready to merge. Bc. some config variables have currently missed the query is being constructed wrong way and it results with no aggregation and no products.

TODO:

• fix the config parameters in order to get the right query object,
• modify queryBuilder in the graphql resolvers to use this new storefront-query-builder library,

[pkarw]

• The response_format query parameter to the /api/catalog endpoint. Currently there is just one additional format supported: response_format=compact. When used, the response format got optimized by: a) remapping the results, removing the _source from the hits.hits; b) compressing the JSON fields names according to the config.products.fieldsToCompact; c) removing the JSON fields from the product.configurable_children when their values === parent product values; overall response size reduced over -70% - @pkarw
• The support for SearchQuery instead of the ElasticSearch DSL as for the input to /api/catalog - using storefront-query-builder package - @pkarw - Remove Elastic DSL / bodybuilder from frontend vue-storefront#2167

[pkarw]

Thanks! OK I've used # as for now. npm is definitely the right idea: https://www.npmjs.com/package/storefront-query-builder

what's your npm login? @andrzejewsky and yours? I'll add you to the VueStorefront org on npm guys

[ResuBaka]

My Account is resubaka on npm. @pkarw

[ResuBaka]

This should be changed to 0.0.*

So we don't get possible breaking changes, as 0.1.0 could have breaking changes in it when you go after semver versioning.