Latest release doesn't have most recent fixes: Could not parse the filter query: unbalanced && operands.

[robjbrain]

Description

I'm just doing what I think is the most basic usage of the library.

Model::search('myterm');

But i'm getting the following error:

"Could not parse the filter query: unbalanced && operands."

It looks like this was fixed a month ago: 7a9edba#diff-30cbc8fb802094edb92485725f009b63a895bcc546b84381b550883a17441129R266

However there hasn't been a new release since July so composer is still picking up the old version.

How can I get the latest version?

As it stands right now it seems like this package doesn't work out of the box.

I am on 5.1.0 right now.

[Mwakashem]

FACING THE SAME ISSUE

[Mwakashem]

Found a way, Coppied the changed files above 7a9edba#diff-30cbc8fb802094edb92485725f009b63a895bcc546b84381b550883a17441129R266
THIS FILE
https://github.com/typesense/laravel-scout-typesense-driver/blob/7a9edba9d8259c51db391438564996968a8db82b/src/Engines/TypesenseEngine.php
and replaced the ones i have with them. It worked

[mattmcardle]

Also facing this issue, back to meilisearch for me :(

[robjbrain]

Use dev-master in your composer.json instead and it should fix it.

"typesense/laravel-scout-typesense-driver": "dev-master"

[mattmcardle]

@robjbrain thanks, that seems to have resolved this error, although I'm now encountering #45 😢
Rolling back to 5.1 to run the import, then upgrading to dev-master to get around this issue works though, this has dented my confidence in typesense a bit and I'm not sure if this package is fit for production.

[jasonbosco]

I’m sorry about the mess here. Part of the problem is that we didn’t have a test suite for this community-contributed library and we continued to make changes to it without adding a test suite, even once we adopted it into the Typesense org. So that let an import bug make its way into a release.

So we rolled back and have now prioritized writing an automated test suite that will run in CI, before we push out any more releases.

Hopefully that will prevent future issues like this.

[manavo]

@jasonbosco could we get a release to add support for Laravel 10 (merged today), even before the test suite is ready? If there are no other changes?

[karakhanyans]

@manavo @robjbrain

Latest changes are now released, they are in v5.2.1 release.

Sorry for any inconvenience.