Nope, the problem is not due to the magical nature of the framework. They implemented the JSON decoder with a JSON to YAML converter, passing that through the

Nope, the problem is not due to the magical nature of the framework. They implemented the JSON decoder with a JSON to YAML converter, passing that through the YAML decoder. The fix involves using an actual JSON parser and skip the going through YAML part. So it does qualify as a JSON parser bug, IMO (which is what I clumsily attempted to imply with my "(or JSON)" clause above.)