Make It Hard to Write Bad Code
javascript.works-hub.com
Make It Hard to Write Bad Code
1–8 of 8 posts
Re: Make It Hard to Write Bad Code
#2No no no. Linters. God. I tried them and none of them managed to play nice with all the various libraries... All I got was a mass of ugly highlighted 'wrong' code.
This after I painstakingly made my own linting rules.
Re: Make It Hard to Write Bad Code
#3No no no. Linters. God. I tried them and none of them managed to play nice with all the various libraries... All I got was a mass of ugly highlighted 'wrong' code. This after I painstakingly made my own linting rules.
Seemed to work fine with me in Atom? What text editor do you use?
Re: Make It Hard to Write Bad Code
#4I use sublime, works pretty well on that too
Re: Make It Hard to Write Bad Code
#5eslint and tslint are fantastically helpful tools for code quality.
Re: Make It Hard to Write Bad Code
#6No no no. Linters. God. I tried them and none of them managed to play nice with all the various libraries... All I got was a mass of ugly highlighted 'wrong' code. This after I painstakingly made my own linting rules.
Seemed to work fine with me in Atom? What text editor do you use?
I use sublime, but I meant that each third party library has their own idea of linting, some use BEM some use camelCase etc.. There's no way to consistently lint them all.
Linting is a great idea in theory but in practice there are way too many 'correct' approaches to writing code.
Re: Make It Hard to Write Bad Code
#7Earlier quoted context omitted.
Seemed to work fine with me in Atom? What text editor do you use?
I use sublime, but I meant that each third party library has their own idea of linting, some use BEM some use camelCase etc.. There's no way to consistently lint them all. Linting is a great idea in theory but in practice there are way too many 'correct' approaches to writing code.
You shouldn't be linting third party code to begin with.
Re: Make It Hard to Write Bad Code
#8Earlier quoted context omitted.
I use sublime, but I meant that each third party library has their own idea of linting, some use BEM some use camelCase etc.. There's no way to consistently lint them all. Linting is a great idea in theory but in practice there are way too many 'correct' approaches to writing code.
You shouldn't be linting third party code to begin with.
True, but for that I'd need to constantly ignore files from my linter.. Also not an ideal solution.
To clarify this happens more for sass or css projects where variables need to be set according to the base library and linters go nuts over them.