Naming Convention Conflict?

[haleyngonadi]

I have a model called Collection that I have Typesense wired up for. When I do a search, i.e.

keyword = params[:keyword] || "*"
attributes = params[:attributes] || "name"
search = Collection.pagy_search(keyword, attributes)

It immediately throws the error:
NoMethodError (undefined method 'where' for class Typesense::Collection)

I think my Collection model is somehow clashing with Typesense::Collection. Is there a way around this witjout having to rename my model?

[tharropoulos]

Hey @haleyngonadi ,

I dug into it and this does look like a real naming collision in the gem. When typesense stores the model class internally, a model named Collection can get resolved as Typesense::Collection instead of your app's ::Collection. Later, when search loads the records back from hit IDs, it calls .where(...) on that stored class, which is why you end up with that error.

While your Collection model name is the trigger, this should be handled by the integration and shouldn't require you to rename your model. I've put together a fix for this and will merge soon

[haleyngonadi]

@tharropoulos thank you so much!

[jasonbosco]

This is now available in 1.0.0.rc7