Autofixer for newline-after-import. Fixes #686#696
Conversation
|
Keep having this error locally. Can repro on master branch as well. Does anyone know what to do ? |
3e991bf to
6e426c7
Compare
|
@eelyafi i'm quite sure that's a bug in the test; i'll fix it on master momentarily. |
|
@eelyafi actually, are you using |
|
@ljharb I'm using |
|
@eelyafi and is your current working directory the root of the project? or is it inside |
|
also, after running |
|
I was able to reproduce the error by running |
|
@ljharb it helped ! thanks :) |
2 similar comments
|
@ljharb looks like the PR passed all tests but there is no reviewers. How to add one ? |
src/rules/newline-after-import.js
Outdated
| module.exports = { | ||
| meta: { | ||
| docs: {}, | ||
| fixable: 'code', |
There was a problem hiding this comment.
Similar newline-after-var rule in eslint uses the whitespace option. I haven't found the difference between two options in the docs, but just for consistency I'd suggest to use whitespace.
|
any plans on merging this? |
|
I'm sorry @eelyafi, I forgot about this PR, and I merged #742 before I merged this one, which allows the customization of the number of lines after the imports. (sorry again... 😞) |
1e4d07f to
73de417
Compare
|
(This PR is now freshly rebased; thanks @truckingsim for the nudge) |
|
Thanks for letting me know about the rebasing didn't think about that. Appreciate the quick response! |
|
Let's give this a day or two for extra reviews - after that, I'll plan to merge it. |
|
published with v2.5.0. thanks for the (months! of) work and attention on this, everyone! 😁 |
A PR for #686
Will add autofixer for newline-after-import rule.