Enforce JS style guide (again)
See original GitHub issueAs reported in https://groups.google.com/d/msg/wagtail-developers/MjNuJnhXJv4/cPZX5LhnBgAJ - it appears that JS linting was broken when #2275 was merged (npm run lint:js
now only checks the client
folder). We need to:
- fix the task to run across the whole codebase
- add it to the
make lint
task https://github.com/torchbox/wagtail/blob/master/Makefile#L18-L20 - fix the inevitable style violations that have crept in since #1237
- add it to our CI setup
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:10 (10 by maintainers)
Top Results From Across the Web
Google JavaScript Style Guide
1 Introduction. This document serves as the complete definition of Google's coding standards for source code in the JavaScript programming language.
Read more >ESLint: Everything You need to know about setting up a style ...
Again choose according to your need, it is asking these question because, ... Canonical is the most comprehensive code style guide.
Read more >JavaScript Standard Style
JavaScript style guide, linter, and formatter. This module saves you (and others!) time in three ways ... Never give style feedback on a...
Read more >Coding Style - The Modern JavaScript Tutorial
A style guide contains general rules about “how to write” code, e.g. which quotes to use, how many spaces to indent, the maximal...
Read more >JavaScript Style Guides And Beautifiers - AddyOsmani.com
Following a consistent style guide both helps enforce this concept and improves the overall quality of the code we write. This facilitates other ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@thibaudcolas - makes sense.
Hopefully this will become a bit easier when all code is moved to the webpack build process (client folder)
cc @jonnyscholes
thanks @thibaudcolas