Output

go-json-unmarshalling-output

Example 1 (works as expected with both fields included on struct):
JSON: {"_eventId": "cased"}
_eventid: 
_eventId: cased

Example 2 (works as expected with both fields included on struct):
JSON: {"_eventid": "no case"}
_eventid: no case
_eventId: 

Example 3 (works as expected with both fields included on struct):
JSON: {"_eventid": "no case", "_eventId": "cased"}
_eventid: no case
_eventId: cased

Example 4 (works as expected with both fields included on struct):
JSON: {"_eventId": "cased", "_eventid": "no case"}
_eventid: no case
_eventId: cased

Example 5 (expected empty string):
JSON: {"_eventId": "cased"}
_eventid: cased

Example 6 (works as expected):
JSON: {"_eventid": "no case"}
_eventid: no case

Example 7 (note how the JSON field ordering matters):
JSON: {"_eventid": "no case", "_eventId": "cased"}
_eventid: cased

Example 8 (note how the JSON field ordering matters):
JSON: {"_eventId": "cased", "_eventid": "no case"}
_eventid: no case

Example 9 (works as expected):
JSON: {"_eventId": "cased"}
_eventId: cased

Example 10 (expected empty string):
JSON: {"_eventid": "no case"}
_eventId: no case

Example 11 (note how the JSON field ordering matters):
JSON: {"_eventid": "no case", "_eventId": "cased"}
_eventId: cased

Example 12 (note how the JSON field ordering matters):
JSON: {"_eventId": "cased", "_eventid": "no case"}
_eventId: no case