mirror of
https://gerrit.wikimedia.org/r/mediawiki/extensions/VisualEditor
synced 2024-11-24 06:24:08 +00:00
bedbebd53c
This has no influence on Jenkins but can be used locally to easily run certain tools. Since we already had `.jshintrc` in our repo it was already possible to easily run JSHint from the command-line locally. Taking that as a base the following are new features: * `grunt csslint`: Runs CSSLint on all css files * `grunt qunit`: Runs QUnit (standalone) tests in PhantomJS * `grunt test`: Runs jshint/csslint/qunit * `grunt watch`: Runs the "test" command automatically whenever a file is changed. You can keep this in the background so whenever you save a file in your editor (e.g. Sublime Text) it'll run the tests and if there is a failure, it'll throw a bash error code causing your Terminal application to beep you in whatever way your operating system does so (e.g. for Mac OS X a red badge + jumping icon in the Dock). It will continue to run in the background even after a failure so no need to re-start watch after a failure. * `grunt`: Runs the default task, which is 'test'. Previously to use `jshint .` you had to: * One-time install: * install package -- nodejs npm * npm install -g jshint * Usage: * cd VisualEditor; jshint . Now, for grunt: * One-time install: * install package -- nodejs npm * npm install -g grunt-cli * cd VisualEditor; npm install * Usage: * cd VisualEditor; grunt Change-Id: I7a4fdf4b6bf3f00cef15dc3e2c81eceb595aec7c |
||
---|---|---|
.docs | ||
demos | ||
maintenance | ||
modules | ||
.csslintrc | ||
.gitignore | ||
.gitreview | ||
.jshintignore | ||
.jshintrc | ||
ApiVisualEditor.php | ||
AUTHORS.txt | ||
CODING.md | ||
Gruntfile.js | ||
LICENSE.txt | ||
package.json | ||
README.txt | ||
VisualEditor.hooks.php | ||
VisualEditor.i18n.php | ||
VisualEditor.php | ||
VisualEditorMessagesModule.php |
VisualEditor provides a visual editor for wiki pages. It is written in JavaScript and runs in a web browser. It uses the Parsoid parser to convert wikitext documents to annotated HTML which the VisualEditor is able to load, modify and emit back to Parsoid at which point it is converted back into wikitext. For more information about these projects, check out the wiki: * http://www.mediawiki.org/wiki/VisualEditor * http://www.mediawiki.org/wiki/Parsoid