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

Using the else keyword shouldn't always requires a body #2203

Closed
patrick-east opened this issue Mar 20, 2020 · 0 comments · Fixed by #2219
Closed

Using the else keyword shouldn't always requires a body #2203

patrick-east opened this issue Mar 20, 2020 · 0 comments · Fixed by #2219

Comments

@patrick-east
Copy link
Contributor

Expected Behavior

Any other rule body can be omitted with an implicit { true } being used for evaluation.

Ex:

p = 1

really means

p = 1 {
    true
}

So for else rule bodies this should also work..

p = 1 {
    input.x == "foo"
} else = -1

Should mean..

p = 1 {
    input.x == "foo"
} else = -1 {
    true
}

Actual Behavior

The body for the else rule is required:

$ opa parse /tmp/x.rego
1 error occurred: /tmp/x.rego:6: rego_parse_error: no match found
	} else = -1
	          ^

Additional Info

We should be able to just apply the same logic we do for any other rule body for these.

tsandall added a commit to tsandall/opa that referenced this issue Mar 25, 2020
This commit replaces the existing PEG generated parser with a parser
implemented by hand. The new parser is more efficient (avoiding old
problems with pathological input cases like {{{{{{{{{}}}}}}}} and
deeply-nested composites in general) and offers better opportunities
for improved error reporting (which has been improved already but
there is still room to grow.)

During the test process of implementing the new parser, we identified
a few issues that were present in the old parser. Those issues are
fixed by this commit.

Fixes open-policy-agent#1251
Fixes open-policy-agent#501
Fixes open-policy-agent#2198
Fixes open-policy-agent#2199
Fixes open-policy-agent#2200
Fixes open-policy-agent#2201
Fixes open-policy-agent#2202
Fixes open-policy-agent#2203

Co-authored-by: Torin Sandall <torinsandall@gmail.com>
Co-authored-by: Patrick East <east.patrick@gmail.com>

Signed-off-by: Torin Sandall <torinsandall@gmail.com>
Signed-off-by: Patrick East <east.patrick@gmail.com>
tsandall added a commit that referenced this issue Mar 26, 2020
This commit replaces the existing PEG generated parser with a parser
implemented by hand. The new parser is more efficient (avoiding old
problems with pathological input cases like {{{{{{{{{}}}}}}}} and
deeply-nested composites in general) and offers better opportunities
for improved error reporting (which has been improved already but
there is still room to grow.)

During the test process of implementing the new parser, we identified
a few issues that were present in the old parser. Those issues are
fixed by this commit.

Fixes #1251
Fixes #501
Fixes #2198
Fixes #2199
Fixes #2200
Fixes #2201
Fixes #2202
Fixes #2203

Co-authored-by: Torin Sandall <torinsandall@gmail.com>
Co-authored-by: Patrick East <east.patrick@gmail.com>

Signed-off-by: Torin Sandall <torinsandall@gmail.com>
Signed-off-by: Patrick East <east.patrick@gmail.com>
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

Successfully merging a pull request may close this issue.

1 participant