I actually think this is a great idea. There are a few immediate questions I have though.
1) how does one define a key with a ": "
2) as others said, significant whitespace, specifically trailing, seems to lead problems with keys that have nested key/val, array, multiline string.
3) the github repo associated with the parser has an isue that questions how to verify if the file was truncated.
I think Deco: https://github.com/Enhex/Deco better solves the problem the OP has. It is provably delimiter collision free, unlike this (see my point 1 Unless I'm mistaken).
1) how does one define a key with a ": "
2) as others said, significant whitespace, specifically trailing, seems to lead problems with keys that have nested key/val, array, multiline string.
3) the github repo associated with the parser has an isue that questions how to verify if the file was truncated.
I think Deco: https://github.com/Enhex/Deco better solves the problem the OP has. It is provably delimiter collision free, unlike this (see my point 1 Unless I'm mistaken).