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

Typo in no-duplicate-imports Rule Documentation #11999

Labels
accepted There is consensus among the team that this change meets the criteria for inclusion archived due to age This issue has been archived; please open a new issue for any further discussion documentation Relates to ESLint's documentation rule Relates to ESLint's core rules

Comments

@olsonek
Copy link
Contributor

olsonek commented Jul 16, 2019

I believe there is a typo in the Rule Details section for no-duplicate-imports.

This rules requires that all imports from a single module exists in a single import statement.

I will make a PR to resolve this issue shortly.

@olsonek olsonek added core Relates to ESLint's core APIs and features enhancement This change enhances an existing feature of ESLint triage An ESLint team member will look at this issue soon labels Jul 16, 2019
olsonek added a commit to olsonek/eslint that referenced this issue Jul 16, 2019
@platinumazure platinumazure added documentation Relates to ESLint's documentation evaluating The team will evaluate this issue to decide whether it meets the criteria for inclusion rule Relates to ESLint's core rules accepted There is consensus among the team that this change meets the criteria for inclusion and removed core Relates to ESLint's core APIs and features enhancement This change enhances an existing feature of ESLint triage An ESLint team member will look at this issue soon evaluating The team will evaluate this issue to decide whether it meets the criteria for inclusion labels Jul 16, 2019
@platinumazure
Copy link
Member

Hi @olsonek, thanks for the issue.

I agree this is a typo/mistake. Thanks for creating an issue and I look forward to your pull request!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.