Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Meilisearch Ruby now expects snake_cased attributes instead of camelCase. #311

Closed
coder2000 opened this issue Dec 6, 2023 · 8 comments
Closed
Labels
bug Something isn't working

Comments

@coder2000
Copy link
Contributor

Description
Deprecation warning with current Meilisearch Ruby version says that attributes will need to be snake_case in future versions.

Screenshots or Logs

Attributes will be expected to be snake_case in future versions of Meilisearch Ruby.

Non-conforming attributes: filterableAttributes, sortableAttributes
@ellnix
Copy link
Collaborator

ellnix commented Dec 11, 2023

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

@coder2000
Copy link
Contributor Author

Here it is, and it is all configuration blocks not just one.

  meilisearch do
    attribute :name, :brand_name, :state_name, :created_at, :region_name, :brand_id

    attribute :state_abbr do
      state_abbreviation
    end

    attribute :store_chain do
      store_chain_name || "Independent"
    end

    attribute :region_id do
      region.id
    end

    filterable_attributes [:brand_name, :state_abbr, :region_name, :region_id, :brand_id]
    sortable_attributes [:state_name, :brand_name, :region_name, :store_chain, :name]
  end

@curquiza curquiza added the bug Something isn't working label Jan 3, 2024
@ellnix
Copy link
Collaborator

ellnix commented Jan 11, 2024

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 appear in the source code at all, and this warning does occur in the test suite even though it has many meilisearch blocks.

Some follow up questions if you don't mind answering:

  1. Are you manually creating a meilisearch index anywhere in your code?
  2. When precisely does this happen? After a record is created, when a search is run, when the app launches?
  3. Are you manually adding documents to the ms index anywhere?

@coder2000
Copy link
Contributor Author

  1. What do you mean? I only have the meilisearch blocks on my models
  2. It happens when a record is added or updated
  3. Again what exactly do you mean by manual? With the rails console?

@ellnix
Copy link
Collaborator

ellnix commented Jan 15, 2024

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. Again what exactly do you mean by manual? With the rails console?

By manual I meant doing something like Product.index.add_documents(...) directly (judging from your response you are not doing that). I will look into this and try to reproduce it again.

@brunoocasali
Copy link
Member

@coder2000, are you still having the issue after @ellnix's help? Can you confirm your gems (meilisearch-ruby and meilisearch-rails are the latest?

@ellnix
Copy link
Collaborator

ellnix commented Feb 14, 2024

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.

@coder2000
Copy link
Contributor Author

I'm not seeing this anymore with the latest version of the gem so I will close it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants