My main gripe has been the surprise-causing UX.
If I set one or more keys for a map, I expect only those keys to change, not for the rest of the keys to reset (which reset to HTML in the case of outputs).
I can understand that you don’t prefer generating RSS, but the default behavior of outputs is to generate them. The issue is that the unset default works on the preference to have RSS, while the default after setting works on the preference to not have them.
The frontmatter is a little bit different beast… You can add/override.
From the UX point of view, that’s how the addition/overriding of any key in any config map should work… it’s the path to least surprises, and more convenience (why should I manually set half a dozen keys just because the tool reset them all, when in fact I wanted to update only one key?).
Going forward, it would be nice to be able to add/override selected keys in future config maps… and hopefully the existing maps like outputs also start doing so at some point.
I voted anonymously.