Support for identifying specific lines that are the source of the violation

[jalseth]

Some parsers include metadata about the originating source location and file for entries in the JSON output. Rego policies can include this in the violation object returned to conftest. conftest would consume this and include it in a new field in the output.Result struct. Each outputter could decide on the best way to surface this to users.

For example, the github outputter may emit an additional line that points to the origin file, and update the message in the tested file.

[anderseknert]

Do you know of any Go parser for JSON that records locations? It's been a while, but I found nothing last time I looked. Having Regal's language server (in particular, but there are more use cases) highlight the parts of a JSON document that violate policy would be amazing.

[jalseth]

I haven't tested it, but this one seems to have the location of each token https://pkg.go.dev/github.com/rafaelmgr12/jingo@v0.0.0-20250218200502-5230a95e962d/pkg/parser#Token.

[anderseknert]

Neat, I'll have to try it out. Thanks :)