v0.13.3 💎

Changes

• Add ability to set timeout and max_retries option during Client instanciation (#86) @bronislav
  => See this README section

Thanks again to @bronislav! 🎉

v0.13.2 💎

Changes

• Update dependencies

This gem is now compatible with MeiliSearch v0.14.0 without any changes in this gem! Enjoy!

Thanks again to @eskombro! 🎉

v0.13.1 💎 [Not available on RubyGems]

No change

v0.13.0 💎

Breaking changes

• Remove sysinfo routes (#75) @curquiza
• Seach route: use POST instead of GET and add tests for placeholder (#77) @curquiza
• Update settings following the settings behavior changes on MeiliSearch (#78) @curquiza

v0.12.0 💎

Changes

• Create CONTRIBUTING.md (#64) @curquiza
• Implement the get_or_create_index method (#69) @curquiza

Breaking changes

• Improve error handler (#65) @curquiza

v0.11.1 💎

Changes

• Add release drafter (#52) @curquiza
• Fix: uid in options does not overwrite the parameter in create_index (#53) @curquiza

v0.11.0

• Refacto and simplify the code for better contributions (#36)
• Fix: Search params crash when they are a list of strings (#42)
• Implement the wait_for_pending_update method (#43)
• Add attributesForFaceting settings routes (#44)
• Implement facets in search using facetFilters and facetsDistribution (#46 and #51)
• Change prototype of create_index and index methods (#50)
• Update README and dependencies

Breaking changes due to the MeiliSearch breaking upgrade (from v0.10.X to v0.11.X)

• in the GET /stats route, the fieldsFrequency attribute is renamed into fieldsDistribution. The value of this attribute does not change. (#39)
• MeiliSearch is currently doing a better error handler. Now, the following attributes are present in the body answer when raising an error: errorCode, errorType and errorLink.
  The message attribute still exists but the value of this field might change for some errors.
  We do not recommend using the content of these fields immediately (wait for the v0.12.0): MeiliSearch is indeed still working on this error handler and the content of these fields will probably change.

Thanks to @eskombro and @curquiza!