Anders Eknert

Having thought more about this, I think the symbols we'll want to cover are: - objects - arrays - comprehensions in other words, anything that increases the nesting level. When...

One idea would be to group violations either by rule, or by file. If we currently have an output like this: ``` Rule: forbidden-function-call Description: Forbidden function call Category: custom...

@rahulkrishnanfs done!

@rahulkrishnanfs did you find some time to take a look at this? 🙂

Thinking more about this, and it's certainly an aggregate rule as we'll need to collect info from all packages to try and determine the type of refs. It's totally fine...

Thanks @asleire! Thinking more about this, I think we could interecept the "[will save document](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_willSave)" event in the language server, and send back a notice (modal) to the client about...

Merging this issue with #3 as I think a single rule to cover this is better, and more likely easier to implement as well. Rather than trying to detect if...

For the API case — but likely also for us to display nice output of errors in the CLI, I suppose it would make sense for us to create, and...

This is "blocked" by https://github.com/open-policy-agent/opa/issues/5815 Most of these should be easy to implement using the AST alone, so will probably go with that rather than relying on the compiler. First...

Current status: - [x] Duplicate imports - [ ] Unused local assignments - [ ] Unused imports - [x] `input` and `data` reserved keywords - [x] Use of deprecated built-ins...