Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
z1haze opened this issue May 7, 2024 · 0 comments
Open

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

z1haze opened this issue May 7, 2024 · 0 comments

Comments

@z1haze
Copy link

z1haze commented May 7, 2024

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,
    },
  ],
};
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant