Built-in namespacing #314
Comments
tsandall
added a commit
to tsandall/opa
that referenced
this issue
May 12, 2017
This change updates the grammar so that built-in names can contain
periods ("."). This allows built-in names to be namespaced which will be
important down the road once people start adding custom built-ins.
Fixes open-policy-agent#314
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Eventually we'll end up with custom built-ins or upstream built-ins to work with data from from specific, well-known projects. Either way, we should have a way of namespacing them for clarity and to avoid conflicts.
Today, built-ins are all of the form
<name: var>(<op1: term>, <op2: term>, ...). We could namespace built-ins as follows:<name: ref>(<op1: term>, <op2: term>, ...). E.g.,my.special.builtin.func("foo").The text was updated successfully, but these errors were encountered: