Not sure if this is related but I have this query: '$filter=test eq 12345'

And this is what I am getting:

{
"name": "SyntaxError",
"expected": [
"" "",
""&""
],
"found": "2",
"message": "Expected " " or "&" but "2" found.",
"offset": 17,
"line": 1,
"column": 18
}
Am I doing something wrong?

Thanks.

Im experiencing the same issue.

odata.parse('$filter=Temperature gt 50');

yields the expression object:

{
'$filter': {
type: 'gt',
left: { type: 'property', name: 'Temperature' },
right: { type: 'literal', value: 5 }
}
}

Any word on a resolution for this? I just found this library to hook into my code to help translate $filter strings to MySQL where clauses and this is a show-stopper for me.

To see the problem change the test:

it('should parse numbers okay', function(){
var ast = parser.parse('$filter=status eq 35');
assert.equal(ast.$filter.right.value, 35); // this will fail is it will be 3
});

A "quick and dirty" workaround could be commenting out lines byte /' and sbyte / from the primitiveLiteral specification in src/odata.pegjs and running npm prepublish to get the lib/odata-parser.js updated.

There seems to be a problem with parsing integers and the order of processing of integers and bytes.