Anders Eknert

Agreed, but fine to ignore until someone else asks about it.

Fair point about editors. I guess a simple way to avoid that would be to say that `##` _and_ a valid metadata attribute starts a metadata block, so this would...

Although that's an interesting idea, I think that's one step too far 😅 I think it's good to keep metadata as comments, as it feels like they logically belong in...

Hi @zregvart, and thanks for reporting this 👍 Looks like the formatter calls the `String()` method on the term, which delegates to [strconv.Quote](https://github.com/open-policy-agent/opa/blob/main/ast/term.go#L801) and that's where the string is transformed...

Yep, I think any character that's valid JSON should be allowed, and as far as I know, using `\u0000` to represent unicode null is valid, so the formatter should leave...

[ODM](https://github.com/johanfylling/opa-dependency-manager/) is a really cool side project by @johanfylling exploring this space. Early stage still, but definitely looks promising.

> Ultimately, it would be nice to create the ability to view, share, and collaborate on policies. Agreed, although I think GitHub (or GitLab, or whatever) is the better place...

This is similar to the oddness I encountered some week ago, where forgetting to import future keywords would still allow the "if" construct — it would just do something else...

I looked into this for a rule in [Regal](https://github.com/StyraInc/regal), but I think the recommendation here would be to automatically format the package using `opa fmt`, which would reformat the code...

Replacing the no longer `future` import with `rego.v1` and this is a compile time error: ```rego 1 error occurred: policy.rego:5: rego_parse_error: `if` keyword is required before rule body ``` Since...