Skip to content

Commit a7d27ef

Browse files
authored
Add Rego v1 keywords (#6649)
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 <[email protected]>
1 parent d3a4a87 commit a7d27ef

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

docs/content/policy-reference.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1316,10 +1316,16 @@ names, or dot-access style reference arguments:
13161316

13171317
```
13181318
as
1319+
contains
1320+
data
13191321
default
13201322
else
1323+
every
13211324
false
1325+
if
1326+
in
13221327
import
1328+
input
13231329
package
13241330
not
13251331
null
@@ -1381,7 +1387,7 @@ non-empty-set = "{" term { "," term } "}"
13811387
empty-set = "set(" ")"
13821388
```
13831389

1384-
Note that the grammar corresponds to Rego with all future keywords enabled.
1390+
Note that the grammar corresponds to Rego with `rego.v1` enabled.
13851391

13861392
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:
13871393

0 commit comments

Comments
 (0)