Board Thread:Watercooler/@comment-24473195-20160526110434

There are several occasions when a script needs minor tweaks to the configuration to suit an end-user. However currently the norm is to store those configurations internally which causes issues:


 * Requires a new script review
 * End-user may make a mistake and render the script unusable
 * Localization becomes cumbersome and error-prone with huge scripts
 * No validation of configuration

One idea is to change the current norm, and store them separately:


 * Script / i18n.json
 * Script / config.json
 * Script / data.json or MediaWiki:Custom-scriptname-data.json

Data can contain any relevant data, such as words.

This will reduce the amount of time for review, make localization a breeze (tools can even be made for it), and make it easier to port to a future Gadgets extension (if it ever gets deployed).

I've partly done this using a simple function in Jumbles:

 