Comparison with other packages?

[tony]

Hi! Thank you for the project.

Is their any comparison between this project and https://github.com/gajus/liqe? Are their any similar, active projects out there that also use TypeScript and parse lucene-like queries to AST?

[oxdev03]

Hi,

Initially, I wanted to use Liqe, but it has a bug that doesn't support numbers in queries. As a result, I decided to create an npm package that offers more customization options, such as variables and functions.

Performance-wise, both are fast, and I didn't notice any significant difference in my initial tests. There are other Lucene-like parsers available, but their last commits were over five years ago. That’s another reason I decided to create this repository.

Are you missing a feature or looking for something specific?

Best regards

[tony]

Hi,

Thank you for the explanation behind the project and about the Liqe package as well.

There are other Lucene-like parsers available, but their last commits were over five years ago. That’s another reason I decided to create this repository.

Yes, I've noticed the same when searching for libraries regarding these, the ecosystem is a bit ad hoc, and outdated packages tend to run into issues (Not supporting ESM, TypeScript, having bugs, so on).

Are you missing a feature or looking for something specific?

Yes, do you offer or have any of these on your roadmap?

• Schemas: Autocompletion and validation

  e.g. for the example at Search and filtering usage, would gender, firstName, and age be handled against a schema / model? Example: FieldSchema in search-input-query-parser.

• UX widget

  Example: search-input-query-react is doing:

  Demo

  

  Credit: @williamcotton via search-input-query-demo.

[oxdev03]

Hi,
currently none of the features are planned.
The first sounds reasonable and I might consider it.

Is this a validation pre or post filtering?

I am not sure if the Widget is feasible and currently worth the implementation effort

Kind Regards,
oxdev03

[tony]

Hi and thank you for the follow up!

In regards to schemas: I assume the validation is pre-filtering, e.g. if name:john is entered, ensuring that name is defined in the schema and that john is a string. I haven't used the package thoroughly yet.

I am not sure if the Widget is feasible and currently worth the implementation effort

No worries, given the goal of this project I am happy you built it and it does what it does!

That is it from me - I am fine if you close this if there's nothing else!

If you do take up the idea of having a schema of some sort that may be interesting!