Anders Eknert

@charlieegan3 it does make sense, although it's hard to say where the responsibilities of the formatter starts and ends. I could imagine this as a linter rule just as well....

Cool! I hope we'll see more progress there 😃 Great work so far @kitagry 👍

Of course! 👍

@fioreale if you'd want to help review / test the PR later, that'd be welcome!

Agreed!

Running this against OPA v0.58.0, compilation fails with: ``` $ opa build p.rego error: p.rego: 1 error occurred: p.rego:11: rego_type_error: or: arity mismatch have: (string) want: (set[any],set[any]) ``` Whether accidentally...

@tsandall @koponen-styra @srenatus OK to close?

Sounds like this would be a rather simple addition then, and without adding dependencies? If so, I'd just go ahead and write some code for submitting a PR :)

So, this is actually possible already, using the undocumented inline format. ``` # METADATA # schemas: # - input: {"$ref": "http://localhost:8000/schema.json"} ``` As this is about to be both documented,...

I'm using both `rego.Load` and `rego.ParsedBundle` without passing any transaction. I'm not sure I follow :)