-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
AST: missing location in some rule head refs #6860
Comments
can I pick this up ?? ...it would be my first to contribute to opa codebase |
Certainly @kd-labs! Let us know how if you run into any issues. Reviewing https://github.com/open-policy-agent/opa/pull/5576/files might be a good place to start. |
This issue has been automatically marked as inactive because it has not had any activity in the last 30 days. Although currently inactive, the issue could still be considered and actively worked on in the future. More details about the use-case this issue attempts to address, the value provided by completing it or possible solutions to resolve it would help to prioritize the issue. |
When the JSON option to include term locations have been set, they should be included in all parts of the head where terms appear. Fixes open-policy-agent#6860 Signed-off-by: Anders Eknert <anders@styra.com>
When the JSON option to include term locations have been set, they should be included in all parts of the head where terms appear. Fixes open-policy-agent#6860 Signed-off-by: Anders Eknert <anders@styra.com>
When the JSON option to include term locations have been set, they should be included in all parts of the head where terms appear. Fixes #6860 Signed-off-by: Anders Eknert <anders@styra.com>
This was reported in Regal, but my brief investigation suggests that the issue originates in OPA. Regal expects each part of a ref to include a
location
. However, a policy like this:Transforms to an AST where the first
a.b
has no ref locations, and the seconda.b
does.rule.head.ref "a.b if true"
rule.head.ref "a.b := true"
I believe this inconsistency is a bug.
The text was updated successfully, but these errors were encountered: