Skip to content

Commit

Permalink
Add Rego v1 keywords (#6649)
Browse files Browse the repository at this point in the history
Let me know if these should be in a box of their own — my reasoning
was that they should be avoided even prior to that, so if people won't
use them as var names or whatever, all the better.

Signed-off-by: Anders Eknert <anders@eknert.com>
  • Loading branch information
anderseknert authored Mar 28, 2024
1 parent d3a4a87 commit a7d27ef
Showing 1 changed file with 7 additions and 1 deletion.
8 changes: 7 additions & 1 deletion docs/content/policy-reference.md
Original file line number Diff line number Diff line change
Expand Up @@ -1316,10 +1316,16 @@ names, or dot-access style reference arguments:

```
as
contains
data
default
else
every
false
if
in
import
input
package
not
null
Expand Down Expand Up @@ -1381,7 +1387,7 @@ non-empty-set = "{" term { "," term } "}"
empty-set = "set(" ")"
```

Note that the grammar corresponds to Rego with all future keywords enabled.
Note that the grammar corresponds to Rego with `rego.v1` enabled.

The grammar defined above makes use of the following syntax. See [the Wikipedia page on EBNF](https://en.wikipedia.org/wiki/Extended_Backus–Naur_Form) for more details:

Expand Down

0 comments on commit a7d27ef

Please sign in to comment.