Skip to content
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

Expose ESLint's --format already. #1286

Open
laino opened this issue Jun 2, 2019 · 1 comment

Comments

@laino
Copy link

commented Jun 2, 2019

The default reporter lacks information compared to the output of (for example) the JSON reporter.

This makes linting in all IDEs using standard terrible by default.

I realize this has been discussed already, but the closing argument didn't make much sense, because

  1. If there was any gatekeeping, it would be done by eslint
  2. There is no gatekeeping because you can use custom formatters anyways.

I'm trying to modernize and improve the eslint linter in vim's ale right now by migrating it to JSON, but for now I have to keep the old code around just to keep this linter working.

The main feature that is missing with the default output is getting proper "endColumn" values.

@laino

This comment has been minimized.

Copy link
Author

commented Jun 2, 2019

For illustrative purposes, here is linting without endColumn values:

image

And linting with endColumn values:

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
You can’t perform that action at this time.