Michal

Here `test`, `you`, `brag` and `dog` would be interpreted as variable names – this behavior is baked into Filtrex and there's really no way around. If you're not happy with...

I love your idea, it provides extensibility that fits the library very nicely! However, it seems that @joewalnes lost his interest in this repository a while ago. I'm strongly considering...

I was just randomly browsing the issues and felt a sudden urge to point out this was implemented in the end. Tutorial for a text matcher in filtrex can be...

The issue was caused by NPM not being up-to-date. As of 2019 this is no longer the case and the NPM package is being actively maintained again.

Hello Mateusz, Thank you for sharing your code! However, I don't think making everything async by default is a good idea. Since most applications don't need async expressions, the code...

@mtsbarbosa I don't think there's a better way than having two `compileExpression`s, or at least an `async` flag that would turn asynchronous functions on. Being able to write synchronous expressions...

Also, the [new filtrex](https://github.com/m93a/filtrex) supports the `of` operator: ```javascript let f = compileExpression('version of software >= 1.4') f({ software: {name: 'Foo', version: 2} }) // true f({ software: {name: 'bar',...

You can define your custom functions for it: ```js let filter = compileExpression( '"31.07." + (month(myDate)

@joewalnes Close this?

The pull request doesn't work on my machine 😕 elementary 5.1 (based on Ubuntu 18.04.3 LTS) XeTeX 3.14159265-2.6-0.99998 (TeX Live 2017/Debian) [Log here.](https://gist.github.com/m93a/6e1457de834454974e22fbb2162a0125)  I tried putting [this definition](https://tex.stackexchange.com/a/195460/51512) before...