User blog comment:Rappy 4187/Tools For Making JavaScript Review Even Easier/@comment-24473195-20160714175325

Nice coverage of the tools.

I'd like to reiterate what DEmersonJMFM noted, and something we've discussed a lot of times in dev.wikia.com. While these tools are fine, they still lack very simple configuration options, one good way to use it is to model it after gadgets:


 * https://www.mediawiki.org/wiki/Extension:Gadgets#Usage

Those basic configuration options could actually be imported and cached when the user gets on a wiki. This would make it way easier to improve things such as :


 * Script localization and internalization
 * Script management (e.g. Gadget 2.0)
 * Reduced reviews

Aside from that, as we discussed before, scripts with fatal errors should be immediately declined, as more often than not the user made a mistake submitting them (see http://dev.wikia.com/wiki/Thread:9373).

One idea would actually be to use the Mediawiki:ImportJS, by adding to each line the configuration option, that would then be extracted to a global variable (e.g. wgWikiaScripts_myfavscript), so in importJS we'd have something like:

dev:test23.js|{ variable:123456, variable2: {ababa} } | dev:test5| ... Usage: wgWikiaScripts_myfavscript.variable -> 123456

Or define a separate file:

dev:test23.js|config.json |

Another idea also discussed would be to backport the options api (https://www.mediawiki.org/wiki/API:Options#Changing_options), and allow scripters to save this information there.

Lastly, and more importantly, there is a need to disable or revert live scripts and at least have 2 approved versions at all times that one can go back and forth from. Perhaps deleting a script automatically "unapproves it" but I'm not sure.

The biggest gain would probably be to help out in improving and fixing up the Extension:gadgets 2.0, and deploy this globally.

Also, thanks for the stats, I always estimated that a relatively small number of users actually changed their JS, and this actually proves it!