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

only show lint messages of the current linting file #304

Closed
wants to merge 525 commits into from

Conversation

liigo
Copy link

@liigo liigo commented Dec 19, 2014

I'm working on Rust Linter, which would like to support Rust's package manager, Cargo. Cargo was designed to build a package (or project), which is a group of many source files. While linting a file inside a package, we build the full package (use Cargo). (You can't just compile only one of these files individually.) There are maybe some errors, cause by files other than the current linting one, which need to be ignored. This PR changes the behavior to only show lint messages of the current linting file.

This is a backward compatible improvement.

dmnd and others added 30 commits August 4, 2014 23:10
Test Plan:
Opened a file, linted, and checked console for errors.
Only widen the gutter when showGutter is enabled
new linter [linter-jsxhint](https://atom.io/packages/linter-jsxhint), for JSX (React.js), using `jsxhint`
Tested this with csslint, pylint, coffeelint on OS X and everything seemed to
work. Since this apparently fixes issues for Windows users, I'm merging it in.
dmnd and others added 8 commits December 10, 2014 21:33
These classes get put on the containing `atom-panel` element with the new panel API.
With lint on change disabled, timing out linters doesn't make as much sense.
I implemented this so I could test out how the linter feels with no timeout.

Fixes steelbrain#204.

Test Plan:
Open a complex Python file for which pylint used to time out. Notice errors
appear after a long time.
computeRange: (match) ->
if match.file?
if match.file isnt @lintingFile
# TODO: show a message to indicate there are errors in other files
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

did you mean show something in treeView?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@hd-deman Perhaps. I know little about Linter itself. Maybe it could be improved in other PR later?

@reem
Copy link

reem commented May 1, 2015

Any news here? This is a big hurdle to using atom with rust.

@iam4x
Copy link
Contributor

iam4x commented May 4, 2015

@hd-deman Can you take care of this one?

@HitomiTenshi
Copy link

Any news on the merge situation?

@bb010g
Copy link

bb010g commented May 21, 2015

bumpity bump

@HitomiTenshi
Copy link

bumping intensifies

@bb010g
Copy link

bb010g commented Jun 24, 2015

Woo!

@AsaAyers
Copy link
Contributor

To be clear this wasn't merged. linter has been completely rewritten so all existing issues were closed at once from #571

I believe this can be solved in linter-rust (or whatever) by migrating to the new API. All linters will be required to migrate to the new API, but the timeline hasn't been set yet.

@liigo
Copy link
Author

liigo commented Jun 26, 2015

To be clear, I'd like to say, I didn't submit soooooooo many commits. I don't known what happens here.

@AsaAyers I'll try new Linter api if possible. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.