expected to not require 'all, any, none' for condition?

[z1haze]

Hi, awesome library btw!

I wanted to ask if it was intentional that you readme shows using conditions without they all/any/none keyword. I'm scanning the code and I see that it will return false in any event that one is not present, although the docs show this as an example:

const rule: Rule = {
  conditions: [
    {
      field: "profile.age",
      operator: ">=",
      value: 18,
    },
  ],
};

[andrewbrg]

Hi @z1haze sorry for the super late reply, I have not checked this repo in a long time. Yea i think it's not correct in the docs, i'll fix it :)