-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Rule proposal: Enforce imports be placed at the top of the file #253
Comments
Sorry, I missed the |
Do you envision this as an option on the |
Ah, lol, right. I also forgot that one. 😅 |
I wouldn't be opposed to moving this into |
I don't see how |
I was thinking that if they are most frequently used together, it might be simpler to make it a single rule. That's fair, though. Could move the opposite direction and take the absolute-first bit out of import-first, too. On Apr 21, 2016, at 21:17, Sindre Sorhus <notifications@git.luolix.topmailto:notifications@github.com> wrote: I don't see how import-first is relevant to ordering though. It's just about enforcing imports at the top, in any order. You are receiving this because you commented. |
👍 Agreed. It doesn't fit there. |
Moved from jfmengels/eslint-plugin-import-order#11.
Imports are hoisted to the top anyways. So better to be explicit about it.
Should either ignore
require
or have an option to ignore it, asrequire
is often used inline and is not hoisted.The text was updated successfully, but these errors were encountered: