The problem is the language specification is poorly defined and full of irregularity and corner cases leading to inconsistent parsers.
Much of the problem comes from YAML allowing unquoted strings giving them nothing to clearly distinguish them from other data types. This leaves parsers in the awkward situation of needing to decide through complicated rules whether a token is a string or something else.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This link summarises some of them:
github.com/cblp/yaml-sucks
The problem is the language specification is poorly defined and full of irregularity and corner cases leading to inconsistent parsers.
Much of the problem comes from YAML allowing unquoted strings giving them nothing to clearly distinguish them from other data types. This leaves parsers in the awkward situation of needing to decide through complicated rules whether a token is a string or something else.