Experimental fields #11
Description
Is there an option to properly handle experimental (and not optional) fields (that may or may not be present in implementation as far as I understand that correctly)?
Currently it evaluates directly as json['field'] which throws 'key not found' exception, breaking the whole thing down.