Talk:Requests for comment/Json Config pages in wiki

Begging the question
Personally, I'm not entirely convinced that shoving blobs of json in wiki pages for configuration is all that great of an idea in the first place. For developers it makes sense (although then there's the question of why developers need to configure things by editing a json blob in a wiki page), but does requiring end users to be able to construct a valid json blob in order to configure some feature really make sense? Anomie (talk) 14:41, 4 December 2013 (UTC)
 * At least two (that i know of) implementations of this exact feature shows that it is needed - there are cases when devs (or techy people) need to easily edit fairly complex configurations, while having access to all the wonderful wiki benefits (listed on the page). Secondly, this extension exists specifically so that it would be possible to construct a json-editing as a form feature in one spot and benefit everyone. --Yurik (talk) 02:58, 17 December 2013 (UTC)
 * Or it shows that two projects used Maslow's hammer. I'm not seeing a list of "wiki benefits" in the page either; I do see a list of "Implemented Features", most of which seem like working around wiki drawbacks versus storing server configuration in the server configuration and using Gerrit for code review. Anomie (talk) 14:11, 17 December 2013 (UTC)

Developer API
I would like to see some interface how developers could fetch and update configs. Also a concrete example (doesn't need to be functional) which implements things like validation would help.--Nikerabbit (talk) 11:56, 17 December 2013 (UTC)