Remove Elastic DSL / bodybuilder from frontend

[pkarw]

What is the motivation for adding/enhancing this feature?

This is related to #2166
bodybuilder is about 200KB - and in fact the Elastic query DSL could be constructed 100% in the vue-storefront-api

In that case the catalog.js endpoint no longer will be raw proxy but it will do the logic which is currently done on frontend.

So, the thing is that vue-storefront-api should get the simple query object and build DSL itself. It will also make vue-storefront-api ... in fact simpler. Because being partially a proxy to Elastic and partially a REST API isn't easy to understand.

What are the acceptance criteria

• bodybuilder removed from vue-storefront dependencies
• we should have this as an config option - as some other implementations can base even directly on bodybuilder we should have an option in both: vue-storefront and vue-storefront-api configs to switch this new mode on/off (default is: on)

@patzick and @mdanilowicz let me know what do You think on that?

[patzick]

I would consider Elasticsearch JS library for that as replacement for bodybuilder.
https://www.elastic.co/guide/en/elasticsearch/client/javascript-api/current/introduction.html

[pkarw]

We removed elasticsearch-js as a bundle size optimization - it's not a way to go for sure.

[pkarw]

Its all about sending the SearchQuery object in plain json to /api/catalog and then construct elasticsearch query in API instead of constructing it in the client.

The SearchAdapter and ElasticsearchQuery classes should be refactored simplified
It should be kept as an option to have the current behavior (building queries in client) for backward compatibility but it should be disabled by default

[pkarw]

@andrzejewsky can you please take care of this one after finishing the tasks from 1.11 please?

[andrzejewsky]

@pkarw yeah, sure 🎉