Bruno Casali

Can you please share your stack trace with me? (this could help me to understand the slowness path of your search request). Since we aim to respond to users below...

Hello everyone, I wasn't able to check this yet, but I promise I will! (I just haven't the time to dig into this we are upgrading the integrations to v0.26...

First of all, sorry for this long waiting period! I had a time, and I did a lot of experiments in the rails and the ruby gems. I had internal...

By the way, @cjilbert504 the meilisearch instance is located in the same region of your app? Do you know how long it takes (on average) for meilisearch to answer your...

@schappim about your situation, indexing is indeed something we need to enhance in our core. Still, I'm almost sure that this is not related to Meilisearch Rails directly unless you...

I'm closing this issue due to inactivity. Feel free to reopen it if needed! Also, I've created this issue https://github.com/meilisearch/meilisearch-rails/issues/193 that could help improve the perceived performance. Thanks for using...

@phdavis1027 I think your branch is failing only in the CI because this package only supports Meilisearch v0.27. And the CI is trying to run it against the v0.28. @bidoubiwa...

Indeed that's a nice addition! Thanks for reporting @JasonBarnabe 🌟

@bidoubiwa Is there a way to create aliases? Because if we adopt a new name, maybe the old name can be used for malicious actions.

> The expectation is to not use $this->client->deleteKey in every test cases? Yes, we can use hooks for this kind of setup/teardown. > As the deleteKey should be executed after...