Documentation forwards to Kendo's filter configuration, but Kendo uses it's own operators

[W1nstar]

Hello,

I've been reading docs and at some point we get forwarded to

https://docs.telerik.com/kendo-ui/api/javascript/data/datasource/configuration/filter

In order to configure our own filters. On that page there are operators that are unknown to the JSDO ablFilter convert method, like "doesnotstartwith"

You can check the method and see there are less than on the docs

https://github.com/progress/JSDO/blob/319202b27d5486ae5023d0351e5a4af4d68f3230/src/progress.util.js#L657

Is it a Kendo propietary thing? Will they ever be implemented?

[edselg]

Hello,

It is a limitation. It looks like "doesnotstartwith" and other operators where added to the Kendo UI DataSource in a recent version after we had implement the filters in the JSDO. The JSDO support for the filters was not updated to match the new operators. I would like to add support for the new operators.

How does this limitation impact you or your customers? BTW, how do you consume the JSDO? Do you install it from npmjs.com.

If we implement the functionality would you be able to use from there? Link:

• https://github.com/progress/JSDO/wiki/How-to-build-npm-packages-for-the-JSDO-from-develop-branch

I hope this helps.

[W1nstar]

It's a very nice operator. At least one I'd use a lot. Without that operator I'm bound to add two fields as filter depending on what I need. For example, if I don't want any record starting with a $ sign, I need to add a gte and a lte operators, wich adds complexity.

I personally went with downloading and modifying the whole package. I had to enable localStorage emulation, but I'm not in a nativescript or web environment, for example. I had that infinite loop issue I posted last summer. So, I put progress.jsdo.js on one of projects folders and worked with it, since I was finding issues that I needed to correct. I keep checking if there's a new version.