New MemberExpression functionality in indent rule is a breaking builds
See original GitHub issueWhat version of ESLint are you using?
3.2.0
What parser (default, Babel-ESLint, etc.) are you using?
default
Please show your full configuration:
indent: 2
What did you do? Please include the actual source code causing the issue.
This throws an error:
var foo = bar.baz()
.bip()
.boop();
What did you expect to happen?
I expected the indentation to be counted from bar
and not var
. Or at least to be able to turn off indentation checking for MemberExpression
s. So I expected no error.
What actually happened? Please include the actual, raw output from ESLint.
error Expected indentation of 2 space characters but found 12
Issue Analytics
- State:
- Created 7 years ago
- Reactions:4
- Comments:28 (27 by maintainers)
Top Results From Across the Web
Make prettier to format like eslint - javascript - Stack Overflow
Parameters are indented but the closing parenthesis is not and then, chained method would be indented the same way parameters are. This doesn't ......
Read more >@typescript-eslint/experimental-utils Code Examples | Snyk
Use Snyk Code to scan source code in minutes - no build needed - and fix issues immediately. Enable here ... function binaryExp(node)...
Read more >@babel/plugin-transform-member-expression-literals | Yarn
Fast, reliable, and secure dependency management.
Read more >indent - ESLint - Pluggable JavaScript Linter
A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.
Read more >Changelog - JSCS
Anyways, there are three new rules, a couple of changes for the airbnb preset and important fixes for disallowSpacesInsideTemplateStringPlaceholders and ...
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
Maybe adding an alerting system would be beneficial for ESLint. It looks like Greenkeeper immediately caused failures on ~100 repos (including our own) after the last ESLint version was pushed, it would be simple to create a script that scrapes that a few minutes after publishing. If a non-major version causes an abnormal amount of Greenkeeper “breaking” PRs, that is probably a pretty good indicator that something is wrong.
@ljharb yes, exactly.