Remove all frontend code analysis: (s)csslint, jscs, jshint.

plone / plone.recipe.codeanalysis

provides static code analysis for Buildout-based Python projects, including flake8, JSHint, CSS Lint, and other code checks

https://pypi.org/project/plone.recipe.codeanalysis/

11 stars 8 forks source link

Remove all frontend code analysis: (s)csslint, jscs, jshint. #231

Closed janjaapdriessen closed 1 year ago

tisto commented 3 years ago

@gyst I don't want to piss off people by removing this if they find it useful. Though, in the long run, I honestly believe this is the right move. We could create a branch with those checkers in place and use a new master branch (maybe with py3 only and without those checkers).

I am also open to share release rights and stuff if someone wants to take over responsibilities on this py2/js-checks branch.

tisto commented 3 years ago

My 2c: The recommended toolchain highly depends on your project. For instance, if you use TypeScript you will have a different toolchain than with vanilla JS. Anyways, this is our current toolchain in Volto (React/vanilla JS):

csslint: replaced with https://stylelint.io/
jscs, jshint: replace with https://eslint.org/ (jscs has merged with ESLint)

In addition, Prettier does a pretty amazing job in the JS community for consistent code-formatting across all kinds of file formats.