example:

var odataFilter = ODataFilterBuilder();

console.log(odataFilter.isEmpty());
// true

I use odata-builder for building large filter from table columns.
Each value can be empty string or undefined value and i want to skip 'contains' operator if value === undefined.

For example:

const filter = {
  name: 'MyName',
  age: undefined  // init value
};

f.build('and').contains('name', filter.name).contains('age', filter.age).toString(); 
// (contains(name, 'MyName')) and (contains(age));

I need to skip contains(age) operator because age === undefined, how to solve this problem?

I noticed the library didn't support the any lambda operator and was curious if it's something trivial to add?

Thoughts?

The library is distributed with ES6 targeted, but to support IE11, would it be possible to target ES5?

I just wanted to confirm that the filter builder does not do any sort of encoding on the output string. I'm not seeing any when looking through the source, but just want to verify.

According to OData:

http://docs.oasis-open.org/odata/odata/v4.0/errata03/os/complete/part2-url-conventions/odata-v4.0-errata03-os-part2-url-conventions-complete.html#_Toc453752335

Note also that the rules in [OData-ABNF] assume that URIs and URI parts have been percent-encoding normalized as described in section 6.2.2.2 of [RFC3986] before applying the grammar to them, i.e. all characters in the unreserved set (see rule unreserved in [OData-ABNF]) are plain literals and not percent-encoded.

Question is, should we add an option to perform the encoding or not?

Thanks!

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• Replace dependency rollup-plugin-terser with @rollup/plugin-terser 0.1.0
• Update dependency eslint to v9
• 🔐 Create all rate-limited PRs at once 🔐

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update dependency @rollup/plugin-babel to v6.0.4
• Update dependency jsdoc to v3.6.11
• Update babel monorepo (@babel/cli, @babel/core, @babel/eslint-parser, @babel/preset-env, @babel/register)
• Update dependency eslint to v8.57.0
• Update dependency rollup to v3.29.4
• Update dependency tsd to v0.31.0
• Update dependency typescript to v5.4.5
• Update jest monorepo to v29.7.0 (babel-jest, jest)
• Update dependency jsdoc to v4
• Update dependency rollup to v4
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

filter.gt('eventDateTime', someDate, true) doesn't produce a filter in the correct OData format. This applies to all filters, not just filter.gt.

ODataV3-V4 datetime filters should be in the following format
(eventDateTime gt 2016-11-16T00:00:00Z) - ISO 8601 and no quotes

Please, can you implement a legacy functional for covering such command as substringof, etc.? Unfortunately, it's not always possible to use the latest oData on backend part. Thank you!

OData version 4 introducses support for the isof function. Documentation is available at https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part2-url-conventions.html#_Toc31361017, however implementation should be fairly straightforward.

Providing only default exports from a module doesn't play well with other module systems. Would it be possible to also export the ODataFilterBuilder as a named export so one might import like:

import { ODataFilterBuilder } from 'odata-filter-builder';

I currently use webpack with a module system of es2015 and target es5. In order to make TypeScript play well with the module, I had to change the export in index.d.ts to:

declare var ODataFilterBuilder: ODataFilterBuilderStatic;
export = ODataFilterBuilder;

and import like:

import * as ODataFilterBuilder from 'odata-filter-builder';

If I don't do that, TypeScript complains with:

Cannot invoke an expression whose type lacks a call signature...

... when trying to use the callable for the ODataFilterBuilder interface:

ODataFilterBuilder('and').eq('foo', 'bar');

Other than that, great library!

I've created an example at https://stackblitz.com/edit/odata-parser-s38vfw

Notice how each of the operators are being wrapped in parenthesis. What I was expecting is a query that looks like:

foo eq 'bar' and quux eq 'baz' and name ne 'bax'

Parenthesis are a "grouping operator" according to the OData specification. Should they be treated as such in the filter builder?

For example, update the filter builder library to specify where they want to group. Another reason to allow grouping as an operator is some implementations of the OData specification don't support the grouping operator.

Right now the filter builder is producing OData strings implying that all implementations support the grouping operator.

Thoughts?

example:

const filter = ODataFilterBuilder().eq('Type/Id', 2);

console.log(ODataFilterBuilder.isODataFilterBuilder(filter));
// true

console.log(ODataFilterBuilder.isODataFilterBuilder({}));
// false