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
Wrong output indentation in all messages if one message has a long multiline quote #6340
Comments
This is a formatter-specific issue. Other formatters may work better for you. Please see the formatter CLI option docs for more options. |
@platinumazure Thank you. However, it seems to be a rather generic problem to be considered for the default formatter. When it appears, it is more easier to correct the error causing quote then to change the formatter. However, the quote in the end of a message queue has an impact on all the queue and should be located and addressed first — and this is somewhat inconvenient. |
It looks like a bug that we should fix. However, I don't think we should fix formatter itself, but instead we should modify |
I will work on this. Just curious about this is intentional behavior? /*eslint newline-per-chained-call:2*/
const http = require('http');
http.request({
}).on('response', response => { // NO ERROR at this `.on`.
}).on('error', error => { // error at this `.on`
}).end(); // error at `.end` Why is the first |
Ah OK. |
What version of ESLint are you using?
2.11.1
What parser (default, Babel-ESLint, etc.) are you using?
default
Please show your full configuration:
What did you do? Please include the actual source code causing the issue.
What did you expect to happen?
An output with readable indentation and alignment.
What actually happened? Please include the actual, raw output from ESLint.
Compare with the output after the last error fixed:
The text was updated successfully, but these errors were encountered: