Skip to content
This repository has been archived by the owner on Aug 7, 2023. It is now read-only.

Use project root as cwd #8

Merged
merged 2 commits into from
Jul 29, 2014
Merged

Use project root as cwd #8

merged 2 commits into from
Jul 29, 2014

Conversation

dmnd
Copy link
Member

@dmnd dmnd commented Jul 8, 2014

I have a pylintrc file in my project root that wasn't being found by
linter-pylint. Looking into it, I discovered @cwd was null because
LinterPylint.constructor never calls super.

Test Plan:
Opened a new Atom window in the directory that contains my pylintrc file and
had pylint import things properly.

I have a pylint file in my project root that wasn't being found by
`linter-pylint`. Looking into it, I discovered `@cwd` was `null` because
`LinterPylint.constructor` never calls `super`.

Test Plan:
Opened a new Atom window in the directory that contains my pylint file and
had pylint import things properly.
dmnd added a commit to dmnd/Linter that referenced this pull request Jul 8, 2014
See AtomLinter/linter-pylint#8 for motivation for this.
It's helpful to use the project root for Python linting at least. I suspect it
would be useful more generally too.

Feel free to close this request if you disagree.

Test Plan:
Crossed fingers
@dmnd
Copy link
Member Author

dmnd commented Jul 14, 2014

Is there any reason not to pull this? steelbrain/linter#127 will obsolete it but it seems people aren't yet convinced this is the right thing for the linter in general.

It's definitely the right thing for pylint though, so can we pull this for now while steelbrain/linter#127 is discussed?

dmnd added a commit that referenced this pull request Jul 29, 2014
@dmnd dmnd merged commit 574005c into AtomLinter:master Jul 29, 2014
@dmnd dmnd deleted the project-root branch August 9, 2014 06:09
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants