Filtering it out from the diffs is one thing, but what will it do when you make a commit? Will it then commit the “filtered content” in the state it was before you enabled the filtering, or as it currently is?
It is flexible in many ways yes, but I don’t quite get how you reach that conclusion. We don’t have anything flexible and universally applicable that doesn’t force you to use the pesky whitespace-based syntax of YAML. A few things can accept JSON, but not JSON5, but you can’t combine different object types in any other format than YAML. But, I’m not complaining per se, few things are that flexible, but that applies to OH as well.
I guess it wouldn’t be too much work to implement a JSON5 alternative to all the YAML stuff, but I don’t think it’s worth the effort just so I don’t have to deal with YAML.
Btw., I just discovered another really bad drawback with YAML: It doesn’t support tab indentation even inside multiline strings. So, it means that everybody that use tabs as indentation, won’t “benefit” from the multiline formatting of scripts. Instead, they will get the script as “one unreadable string with escape characters”, identical to what regular JSON uses. So, it actually “discriminates against” everybody that use tab indentation.
I discovered this while chasing what I thought was a bug in the rules YAML formatting, only to discover that the “bug” is in YAML itself.
edit: I also discovered that JSON5’s “multiline strings” aren’t really multiline, so JSON5 isn’t the alternative I thought it was.