meilisearch-ruby
meilisearch-ruby copied to clipboard
Ruby SDK for the Meilisearch API
Updates the requirements on [rubocop](https://github.com/rubocop/rubocop) to permit the latest version. Release notes Sourced from rubocop's releases. RuboCop 1.35 New features #9364: Add Style/MagicCommentFormat cop. (@dvandersluis, @mattbearman) #10776: New option (consistent)...
We should use better names to our indexes in the tests like this: - https://github.com/meilisearch/meilisearch-ruby/blob/e19ccc50ea636ee48cd394cb5a4c14f9ef2b6251/spec/meilisearch/index/base_spec.rb#L73 - https://github.com/meilisearch/meilisearch-ruby/blob/e19ccc50ea636ee48cd394cb5a4c14f9ef2b6251/spec/meilisearch/index/base_spec.rb#L110 - https://github.com/meilisearch/meilisearch-ruby/blob/e19ccc50ea636ee48cd394cb5a4c14f9ef2b6251/spec/meilisearch/index/base_spec.rb#L5 We can choose books, people, songs, animals, and other simple words...
⚠️ This issue is generated, it means the nameing might be done differently in this package (ex: `add_documents_json` instead of `addDocumentsJson`). Keep the already existing way of naming in this...
We currently support multiple ways of sending the search attributes: - `index.search('abc', { attributesToCrop: ['description'], cropLength: 5 })` - `index.search('abc', { attributes_to_highlight: ['description'] })` and incorrect and weird ways like:...
Some tests are affected if some `Key` leaks from other contexts, breaking some unrelated tests, like this: ``` 3) MeiliSearch::Client - Keys When a client uses default key roles succeeds...
Original discussion https://github.com/meilisearch/meilisearch-ruby/pull/273/files#r779759981 Today we use `!`(bang) operator in some particular cases eg. `create_index!`, `add_documents!`, these methods have something in common, *they wait for the task completion*. After v0.25.0 index...
After #237 #217 which adds snake_case support, we improve our public API to be more idiomatic. But we introduced a new problem regarding the tests. In this [comment](https://github.com/meilisearch/meilisearch-ruby/pull/273/files/014cda4c78ce36677737d90541553899dcca6255#r779147362), I raise...
- [ ] Following the @brunoocasali comment: https://github.com/meilisearch/meilisearch-ruby/pull/273#discussion_r779113900 And following this guide http://blog.plataformatec.com.br/2014/04/improve-your-test-readability-using-the-xunit-structure/ we should update our specs according to this convention to increase the readability. - [ ] We...
Following https://github.com/meilisearch/documentation/blob/090717049e117ffaa3a54baa010883c1c5f90c31/.code-samples.meilisearch.yaml#L1095 and https://github.com/meilisearch/documentation/blob/090717049e117ffaa3a54baa010883c1c5f90c31/.code-samples.meilisearch.yaml#L1103C1-L1103C52 Related to https://github.com/meilisearch/integration-guides/issues/296
> Also, if you have time you could put in your big breaking changing the main class name to `Meilisearch` instead of `MeiliSearch`. Not only here but in the ruby...