Anders Eknert

I think going fully functional would be a mistake, and I say that as someone with several Clojure projects in my GitHub account :) We’d essentially introduce an entirely new...

Better visualization of diffs in assertions would indeed be great, and perhaps a feature request of its own :) A notable difference between that and parameterization though - in your...

Another case, albeit quite a different one, I've been looking at recently is piping kubernetes resource lists into conftest and the like (`kubectl get deployments -o yaml | conftest test...

Circling back to this as I recently had a need for something like this again. BTW, the conftest issue mentioned above has been solved in conftest, and what I wanted...

While `every` is great, it does not help with this issue. Doing iteration over a list of values was possible already before `every`, but won't help with the rest of...

> If the condition attached to the every statement was false for ANY method, the test would fail--which would be identical to how it works in any other rule. Yeah...

Right - it's a cosmetic improvement for sure, but I'd argue that the part that is "still open" **is** the actual parameterization. In some ways, `every` even makes this somewhat...

That seems like a bug @marcaurele 😅 could you provide a snippet showing what that code looks like? (no need to provide all 300 cases, just one or two, and...

Sorry, @ashutosh-narkar, I wasn't clear — I meant it is cumbersome and error-prone to do this in external tools, not in OPA. Adding to that, anything that must be done...

I'm curious to learn more about your use case, as I don't think this request ever came up before :) When/why would someone writing a policy not have access to...