You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The section on FOR ALL in the docs buries the lede (so to speak) by saying that like SQL, Rego does not have a direct way to express FOR ALL. This was true prior to the release of the every keyword, but it's no longer the case. We should revisit this section of the docs and update it to align w/ the new keyword. We should lead w/ every and then mention the alternatives (NOT-SOME-NOT or comprehensions) and explain when those are preferable to every.
The text was updated successfully, but these errors were encountered:
We should really start with `every`, then offer alternatives, and
call out common mistakes in those alternatives after having presented
the proper solution.
Also replaces some one-letter-rule names in the detailled presentation
of `every`.
Fixesopen-policy-agent#4603.
Signed-off-by: Stephan Renatus <[email protected]>
We should really start with `every`, then offer alternatives, and
call out common mistakes in those alternatives after having presented
the proper solution.
Also replaces some one-letter-rule names in the detailled presentation
of `every`.
Fixes#4603.
Signed-off-by: Stephan Renatus <[email protected]>
rokkiter
pushed a commit
to rokkiter/opa
that referenced
this issue
Apr 26, 2022
…policy-agent#4605)
We should really start with `every`, then offer alternatives, and
call out common mistakes in those alternatives after having presented
the proper solution.
Also replaces some one-letter-rule names in the detailled presentation
of `every`.
Fixesopen-policy-agent#4603.
Signed-off-by: Stephan Renatus <[email protected]>
The section on FOR ALL in the docs buries the lede (so to speak) by saying that like SQL, Rego does not have a direct way to express FOR ALL. This was true prior to the release of the every keyword, but it's no longer the case. We should revisit this section of the docs and update it to align w/ the new keyword. We should lead w/
every
and then mention the alternatives (NOT-SOME-NOT or comprehensions) and explain when those are preferable toevery
.The text was updated successfully, but these errors were encountered: