ellnix

Could you provide the meilisearch configuration block in your model that is causing this warning?

It does not happen to me on a brand new rails app and I cannot tell what could be causing the issue. The camel cased `filterableAttributes` and `sortableAttributes` do not...

> 2. It happens when a record is added or updated Thank you > 1. What do you mean? I only have the meilisearch blocks on my models > 3....

I didn't really help in any way. I tried but could not reproduce it, left the issue open to follow up if and when we refactored the gem.

I cannot reproduce this issue. Indeed this error: > ``` > MeiliSearch::CommunicationError: An error occurred while trying to connect to the MeiliSearch instance: Failed to open TCP connection to localhost:7700...

> So maybe the issue is the error is being raised is actually misleading the user @ellnix? Maybe, but this is a `meilisearch-ruby` error, and I cannot see an alternative...

> But thinking more about it, if the user already uses the built-in feature https://github.com/meilisearch/meilisearch-rails/blob/main/README.md#queues--background-jobs I don't think we should even consider the health of meilisearch, because the system will...

I am assuming from your comments that your models have this structure: ```ruby class Author < ApplicationRecord end ``` ```ruby class Post < ApplicationRecord belongs_to :previous_author, class_name: 'Author' # ......

Unfortunately, giving a block to `author` means it will be recognized as a dynamic attribute, not an association (internally therefore there will be no distinction between `body` and `author`, they...

The feature already exists, this is more of a support request. Your error was using `{{VALUE:Actors}}` which is just a CSV of the actors without `linkifyList` applied to them. Instead...