Skip to content

/standard

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

Forbid import of modules using absolute paths (import/no-absolute-path) #1343

Closed
jseminck opened this issue Jul 10, 2017 · 2 comments

Comments

@jseminck
Copy link

commented Jul 10, 2017

The issue you previously reported about this rule should be fixed now, see: benmosher/eslint-plugin-import#803 (comment)

So if you'd like to re-add this rule and try it out again, now would be a good time. If you need help with PR let me know, should be trivial change:

  • bump eslint-plugin-import
  • add the rule again to the config file
@brodybits

This comment has been minimized.

Sign in to view
Copy link
Contributor

commented Jul 18, 2019

Add this to the list for Standard 14 (#1321)?

@feross feross transferred this issue from standard/eslint-config-standard Jul 28, 2019

@feross feross referenced this issue Jul 28, 2019
Closed

@feross feross added this to the standard v14 milestone Jul 28, 2019

@feross feross added accepted enhancement labels Jul 28, 2019

@feross

This comment has been minimized.

Sign in to view
Copy link
Member

commented Jul 28, 2019

This rule will be re-enabled in standard v14.

@feross feross changed the title Re-add rule: no-absolute-path Forbid import of modules using absolute paths (import/no-absolute-path) Jul 28, 2019

@feross feross closed this in 33f3c35 Jul 28, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
accepted enhancement
Milestone
  standard 14
3 participants
@jseminck @brodybits @feross
You can’t perform that action at this time.