operator precedence of AND/OR in where

[kibtidec]

I see in #20 that operator precedence has been improved/fixed. Nevertheless I still observe an issue with AND and OR.

The following two expressions result in the same AST, but shouldn't.

select x from foo where (a or b) and c
select x from foo where a or b and c

Tested with v1.0.0 and also the online demo

[nwronski]

You're right, AND should compose before OR in the second statement. There is an initial fix in master but I will need some more time to test it out before I publish a new release on npm. Thanks!

[kibtidec]

Thank you. Fix works for me and doesn't break any of my existing tests. I will add a few more to see if there are any side effects.

[nwronski]

Released in v1.0.1, thanks!