From a7d27ef1ff391c4c7ee551f24cda27d854d3f299 Mon Sep 17 00:00:00 2001 From: Anders Eknert <anders@styra.com> Date: Thu, 28 Mar 2024 11:27:38 +0100 Subject: [PATCH] Add Rego v1 keywords (#6649) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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> --- docs/content/policy-reference.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/docs/content/policy-reference.md b/docs/content/policy-reference.md index 4f61f3743e..5bdbd968c8 100644 --- a/docs/content/policy-reference.md +++ b/docs/content/policy-reference.md @@ -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 @@ -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: