-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make linting useful #1930
Comments
I added csslint (I think during the stack viewer rewrite) because it did catch and lead to fixes for a lot out-of-spec and broken rules that were causing problems when styling new elements, especially around z-fighting. But I agree the version on travis had become noise because it couldn't be configured in a way meaningful for us. |
I suppose this speaks to a more broad issue with our linting (flake8 especially) - we're not really getting any value out of it while we're accepting so many failures. Even if we ignored some of the more opinionated formatting rules which would be lengthy and disruptive to the git history to fix (e.g. 1500 failures for |
@pgunn is clearly thinking the same, given today's PRs... I have a branch with a more selective flake8 config and am working through some of the low-hanging fruit, let's join forces? |
We're nearly there on a stable config/ quality in #1935 , but there are still a lot of ignored rules which it would be nicer to fix. The remaining rules are:
IMO priorities should be
E731 "don't assign lambdas" may help with mypy. E722 "bare excepts" could at least be |
Should I do PRs to your fork here or do you want to open it up to me as a contributor? |
I should have pushed my branch to the main repo rather than my fork, sorry. Make PRs to my fork for now, hopefully we can get the basic stuff merged soon, which will make it easier. |
csslint is dead; stylelint seems to be today's preferred option. I don't think we get any value out of css linting anyway - it's just 3000 terminal lines (many more lines in the browser) to scroll past on travis. It may have been me who put it in there in the first place. Sorry about that.
The text was updated successfully, but these errors were encountered: