different indentation for function arguments of same nesting level expected
See original GitHub issueVersion: 1.10.3
Parser: default
Rule: "indent": 2
// EX.1 eslint complains
lib.then(function() {
lib.waitFor(function then() {
x = 1;
}, // A
function onTimeout() {
x = 2;
}, // B
500
);
});
// Ex.2 eslint happy
lib.then(function() {
lib.waitFor(function then() {
x = 1;
}, // A
function onTimeout() {
x = 2;
}, // B
500
);
});
this does not appear to be right. A and B are on the same nesting level, yet ESLint approves EX.2 instead of EX.1
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Can a line of Python code know its indentation nesting level?
the two calls to get_nesting_level are at different nesting levels, despite the fact that the leading whitespace is identical.
Read more >Incorrect (potentially) indentation of function arguments ...
I would expect to see this result instead though: function myFunc(arg1 ... Align constructor and function params to have the same indent ......
Read more >Indenting C Programs
"Levels" of Indentation ... The observation to make is that the body of a statement is one level deeper than the statement's own...
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 >PEP 8 – Style Guide for Python Code
Use 4 spaces per indentation level. Continuation lines should align wrapped elements either vertically using Python's implicit line joining ...
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 Free
Top 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
This still potentially affects other people and nothing in eslint has changed, couldn’t this still be open?
we were able to adapt our code-style so it pleases eslint. thank you for the input.