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

Add no-absolute-path rule (fixes #530) #538

Merged
merged 2 commits into from
Sep 1, 2016
Merged

Conversation

jfmengels
Copy link
Collaborator

Add no-absolute-path rule (fixes #530)

@coveralls
Copy link

coveralls commented Aug 30, 2016

Coverage Status

Coverage increased (+0.03%) to 97.757% when pulling b7d454c on no-absolute-path into 28dbed8 on master.

@coveralls
Copy link

coveralls commented Aug 30, 2016

Coverage Status

Coverage increased (+0.03%) to 97.757% when pulling b7d454c on no-absolute-path into 28dbed8 on master.

@@ -8,6 +8,12 @@ import { testContext } from '../utils'
describe('importType(name)', function () {
const context = testContext()

it("should return 'absolute' for node.js modules", function() {
Copy link
Member

Choose a reason for hiding this comment

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

What does 'node.js' mean here?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

That means typo 😅

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Fixed

@benmosher
Copy link
Member

LGTM! :shipit:

@coveralls
Copy link

coveralls commented Sep 1, 2016

Coverage Status

Coverage increased (+0.03%) to 97.757% when pulling b9ec2ef on no-absolute-path into 28dbed8 on master.

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

Successfully merging this pull request may close these issues.

New rule: no-absolute-path
3 participants