Anders Eknert

Boolean values converted to strings not handled properly

2

While developing a [new hook type](https://www.openpolicyagent.org/docs/latest/aws-cloudformation-hooks/) to allow Open Policy Agent (OPA) to make decisions on infrastructure deployments via CloudFormation hooks, one of the challenges we faced was how boolean...

Since the instrumenta image is no longer maintained(?), move to use `openpolicyagent/conftest`.

See docs in PR (and issue) for further details. Fixes #603

As long as the working document parses, inlay hints are recalculated as they should. But if there are parser errors, it looks like we use the last good location. This...

Rule: `impossible-not`

1

This is a mistake I see devs do every now and then — it just never struck me as something we could try and prevent. ```rego deny contains something if...

As per spec https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_signatureHelp While it's possible to get this information by hovering the built-in function, this would help making it easier to get the relevant information for function signatures...

Extend `textDocument/documentSymbol` to cover more symbols

2

With #668 we got basic support for `textDocument/documentSymbol`, which means we currently iterate over all the "public", or top-level identifiers, like packages, rules, functions. This seems to cover the most...

While working on support for [document symbols](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_documentSymbol), one of the open questions was how to best represent Rego's incremental rule definitions for a format that largely expects location _ranges_ for...

As per spec: https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_inlineValue This feature allows the language server to return a list of values that should be presented to the right of a line in the editor, presumably...

As per the spec https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_semanticTokens This provides a more granular "knowledge" about the language than what regex-based syntax highlighting can do, which makes for a more polished overall experience.