JSON

Expected Behavior

As I currently understand it is not possible to make OPA decision based on body contents that has content type application/x-www-form-urlencoded.

Actual Behavior

Decision log says "content-type: application/x-www-form-urlencoded parsing not supported".
Also the parsed_body is empty:
`[
{
"type": "string",
"value": "parsed_body"
},

Hey folks, thanks for a pretty bad ass library! I'm seeing a 3-3.3x gain when decoding fairly large JSON payloads (40-50MB) as compared stdlib/json-iterator.

Few things in the generated code that struck me as odd are the allocation sizes for slices/maps:

• Slice is set to size 1 initially, values are appended using append
• Map does not have a default size specified

Instead of this, I

I'm not sure how feasible this may be, but the old logparser program from Microsoft supported queries like

Select * from test.csv

And it would read from test.csv, without needing any config files.

Hello all,

diff sub-command fails with mysterious error when kubectl version is < 1.18.0.
The error message: exit status 1.

I notice this if condition while debugging the code. It completely hide the real reason why it is failing ...

diff is working fine