-
Improvement
-
Resolution: Fixed
-
Major
-
3.0, 3.2
-
MOODLE_30_STABLE, MOODLE_32_STABLE
-
MOODLE_32_STABLE
-
MDL-52127-master -
Is the JS coding style described here valid?
https://docs.moodle.org/dev/Javascript/Coding_style
If so is there any existing tools to check this automatically?
There's a tool called jscs that could do so if a configuration file was created. It should also be able to semi-interactively create one if pointed at some examples of good practice.
- blocks
-
MDLSITE-4628 Decide JS Coding style for final .eslintrc rules for 3.2 release
- Resolved
-
MDL-54889 Stop using jshint for everything but shifter
- Closed
-
MDL-54939 Make AMD modules eslint warning free
- Closed
- caused a regression
-
MDL-55050 grunt watch causes eslint of all files on any js change.
- Closed
- has a non-specific relationship to
-
MDL-54822 AMD modules using Y global without requiring core/yui
- Closed
-
MDL-54930 Make grunt aware of third party paths
- Closed
- has been marked as being related by
-
MDL-54944 Add the final .eslintrc rules from policy and ensure amd modules remain warning free
- Closed
-
CONTRIB-5862 Problems looking for space around some operators
- Closed
-
MDL-54839 Grunt watch is not working correctly in subdirectories
- Closed
-
MDL-54930 Make grunt aware of third party paths
- Closed
-
MDL-55421 Add eslint config/package definition to earlier branches (partial backport of MDL-52127)
- Closed
- is blocked by
-
MDL-54890 Some JS errors detected in course and assignfeedback_editpdf
- Closed
- is duplicated by
-
MDL-43781 Investigate tools for verifying Javascript coding style
- Closed
-
MDL-53229 JS Code Sniffer
- Closed
- will help resolve
-
MDLSITE-3782 Prechecker jshint check can lead to lots of false positives
- Closed
- links to