- [BUG] When taxons with identical names existed, products were not correctly found.
- [FEATURE] Added a term facet for taxons so we can display counts when showing the taxonomy
Change position of filtering of properties so it influences the facets. Seems more logical.
- Bootstrap setting that indicates if you want the gem to setup your index creation. Set to false in your own application if you want different settings, mappings logic, etc.
- Change default mapping of name to include untouched version that is used for sorting
- Dependency on spree_i18n to enable translations. The translations are also fetched when retrieving the records from the db based on the result of ES
trigrams analyser not available by default. Using snowball.
Changing the ordering of the property facets. First on count, desc, then on term name, asc. Seems more logical. Hopefully elastic search will someday allow sorting on multiple elements.
Add "bootstrap" key to config file because it is mandatory.
Including the css files this way is unnecessary optimisation. Got errors when running in production because files are not available in the asset pipeline. Better to include them in your spree/frontend/all.css file, like everyone else does.
Allow searching on sku
- [BUG] When taxons with identical names existed, products were not correctly found.
- [FEATURE] Added a term facet for taxons so we can display counts when showing the taxonomy
Change position of filtering of properties so it influences the facets. Seems more logical.
- Bootstrap setting that indicates if you want the gem to setup your index creation. Set to false in your own application if you want different settings, mappings logic, etc.
- Change default mapping of name to include untouched version that is used for sorting
- Dependency on spree_i18n to enable translations. The translations are also fetched when retrieving the records from the db based on the result of ES
Changing the ordering of the property facets. First on count, desc, then on term name, asc. Seems more logical. Hopefully elastic search will someday allow sorting on multiple elements.
Add "bootstrap" key to config file because it is mandatory.
Including the css files this way is unnecessary optimisation. Got errors when running in production because files are not available in the asset pipeline. Better to include them in your spree/frontend/all.css file, like everyone else does.
merge
Delete duplicate lines
Merge remote-tracking branch 'upstream/master'