Anders Eknert

Hi @prashant3286! And thank you for offering to help! The issues that are tagged `1.0` are a little special compared to other issues, as they are breaking changes that can't...

Starting out with one of the issues marked as "[good first issue](https://github.com/open-policy-agent/opa/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22)" is a good way to get your feet wet before going after bigger fish :)

Not much point in keeping this open since it isn't included for 1.0. Closing.

Thanks @mosiac1 👍

Spotted in the wild https://github.com/infracost/infracost/blob/032cba294b9c34184eb7616697f0f87d0378e5b8/cmd/jsonschema/main.go#L72

Hi @simar7 👋 Nothing in the works. If someone has the bandwidth to tackle this, that'd be great. As for a workaround, that would be to remove the recursive reference...

FWIW, this is an existing [linter rule](https://docs.styra.com/regal/rules/bugs/invalid-metadata-attribute) in [Regal](https://github.com/styraInc/regal), and has been for quite some time. One problem with the current annotation "syntax" (for lack of a better word), and...

That'd solve the comment issue, but not the verbosity issue :) See the discussion in the issue [here](https://github.com/open-policy-agent/opa/issues/5402#issuecomment-1755780281). I liked @tsandall's suggestion of using a different comment "directive" for metadata...

Closing this after discussion with @johanfylling. [This check](https://docs.styra.com/regal/rules/bugs/invalid-metadata-attribute), and 70+ other linter rules to help enforce a more strict interpretation of Rego are already available in [Regal](https://github.com/styraInc/regal), so adding it...

@tymik it's mostly just an unnamed variable really, but yeah, it could easily be made unsafe as part of this "chaining" of errors reported here.