wasm: composites #1113
Comments
tsandall
added a commit
to tsandall/opa
that referenced
this issue
Jan 20, 2019
These changes add basic support for pattern matching on arrays and objects. Sets and comprehensions not supported yet. Also, as part of these changes, remove the opa_value_not_equal function as it's unnecessary given opa_value_compare. ref open-policy-agent#1113 Signed-off-by: Torin Sandall <torinsandall@gmail.com>
tsandall
added a commit
to tsandall/opa
that referenced
this issue
Jan 20, 2019
These changes update the planner and wasm backend to support array and object literals. For now the literals are constructed dynamically, but in the future we could intern them. Being able to construct them dynamically will be required anyway when comprehensions are added. Fixes open-policy-agent#1113 Signed-off-by: Torin Sandall <torinsandall@gmail.com>
tsandall
added a commit
that referenced
this issue
Jan 21, 2019
These changes add basic support for pattern matching on arrays and objects. Sets and comprehensions not supported yet. Also, as part of these changes, remove the opa_value_not_equal function as it's unnecessary given opa_value_compare. ref #1113 Signed-off-by: Torin Sandall <torinsandall@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The planner and wasm compiler do not support pattern matching operations on composites today. For example, expressions like
input.path = ["posts", id]are not supported yet.The text was updated successfully, but these errors were encountered: