The latest articles on DEV Community by Pedro Lopes (@vjoxyodo). https://dev.to/vjoxyodo https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F81123%2F36a83694-853d-404e-abf9-de8d6525eac0.jpg https://dev.to/vjoxyodo en Pedro Lopes Fri, 06 Jul 2018 10:52:18 +0000 https://dev.to/vjoxyodo/json-client-read-2go8 https://dev.to/vjoxyodo/json-client-read-2go8 <p>Never thought that this would happen in my developer lifetime with multiple clients at the same time.</p> <p>Few months ago I developed a API for data integration with our systems and the API returns always a json data structure schema with 2 keys (output and message). Message key can have multiple string outputs, but output is always 0 (unsuccess) or 1 (success). </p> <p>Two weeks ago I added a new key called guid that contains a uuid (Universally unique identifier), eg.:. 482b8a20-8108-11e8-adc0-fa7ae01bbebc, this implement wouldn't jam with output and/or with message. Suddenly clients said that they are having more output=1 than it is real (btw I track all outputs). So the stupid clients aren't parsing but instead doing a string search in the json schema, so for instance if something like this appears:</p> <p>{“output”: 0,”message”:”something happened”,”txGuid”:”482b8a20-8108-11e8-adc0-fa7ae01bbebc”}</p> <p>They will recognize as 1, since the schema has at least one 1 in the json schema.</p> <p>I tought I have seen everything, but this is definitely a multiple first timer.</p> <p>P.S API Documentation is explicit about json output!</p> json datastructure clientburn clientdevskills