Most (all?) JSON parsers don’t consider duplicate keys as a problem. Why are you concerned about this?
I think you’ll find that other errors, like non-terminated strings, missing curly braces, and other syntax errors will be flagged correctly.
Hi Tim,
Yes other errors like non-terminated strings are giving proper validation erros.
Concern for dup key is because our testing team has this scenario of sending invalid json for the automation testing and they want this case to be failed, but as dup key is not problem for most of snaps so they will get success response. Testing team will expect invalid json error for this but getting success.
We have test pattern in all interfaces for all tools. As apigee and tibco have solution for this.
Apigee has policy regExp and tibco parser has Staxon function for json parsers, so i am looking for similar option in snaps.
Please let me know any thoughts to validate this invalid json due to dup keys.
With Regards,
KumarR
Hi Team,
Below workaround i did to using Python script to validate invalid json -
1-Have binary to doc snap as first snap and land i/p as encodedBase64
2-Add next snap as Script snap with python lang.
Decode back the i/p doc in script and use json.loads module for parsing json it will raise error on dup key.
Refer below link for script-
Thanks,
Kumar
