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

Update Linter.findConfiguration's first parameter to null #39

Merged
merged 1 commit into from
Dec 10, 2015

Conversation

Phylodome
Copy link

Currently, Linter.findConfiguration is called with undefined as
its first parameter. This bypasses tslint's configuration-finding
logic, as it explicitly checks for a null first parameter. Therefore
one cannot use tslint's option to set a tslintConfig attribute in
package.json. This PR corrects that behavior.

Currently, `Linter.findConfiguration` is called with `undefined` as
its first parameter.  This bypasses `tslint`'s configuration-finding
logic, as it explicitly checks for a `null` first parameter.  Therefore
one cannot use `tslint`'s option to set a `tslintConfig` attribute in
`package.json`. This PR corrects that behavior.
@Phylodome Phylodome changed the title Update Linter.findConfiguration's first parameter to null Update Linter.findConfiguration's first parameter to null Dec 10, 2015
@Arcanemagus
Copy link
Member

That is just plain bizarre that it was written like that, this PR looks good to me though!

Arcanemagus added a commit that referenced this pull request Dec 10, 2015
Update Linter.findConfiguration's first parameter to null
@Arcanemagus Arcanemagus merged commit 9a76cef into AtomLinter:master Dec 10, 2015
@Arcanemagus
Copy link
Member

Released in v0.5.1.

@Phylodome
Copy link
Author

Thanks!

@Arcanemagus Arcanemagus added the bug label May 2, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants