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
If a call term was used as a with value, e.g., "p with input as f(1)"
the type checker would panic because the call was not expanded as
expected. These changes update the rewrite term expr stage to rewrite
with values like other AST nodes such as calls and composites.
Also, add an extra test case for with value rewriting to cover open-policy-agent#772.
Fixesopen-policy-agent#916
Signed-off-by: Torin Sandall <torinsandall@gmail.com>
If a call term was used as a with value, e.g., "p with input as f(1)"
the type checker would panic because the call was not expanded as
expected. These changes update the rewrite term expr stage to rewrite
with values like other AST nodes such as calls and composites.
Also, add an extra test case for with value rewriting to cover #772.
Fixes#916
Signed-off-by: Torin Sandall <torinsandall@gmail.com>
I tried to use the result of a function as the input to a test, and caused the syntax parser to panic. Here's a minimal reproduction:
Test number 1 causes the following panic:
Test 2 shows the correct way to do what I was trying to do for anyone else who comes across this problem.
The text was updated successfully, but these errors were encountered: