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 'always-and-inside-groups' value to order's newlines-between option to allow newlines inside import groups #628

Merged
merged 3 commits into from
Jan 22, 2017

Conversation

giodamelio
Copy link
Contributor

New option to allow newlines inside import groups. See #627.

@coveralls
Copy link

coveralls commented Oct 16, 2016

Coverage Status

Coverage increased (+0.003%) to 94.899% when pulling bfd6222 on giodamelio:order-extra-newlines into d9605a0 on benmosher:master.

@coveralls
Copy link

coveralls commented Oct 16, 2016

Coverage Status

Coverage increased (+0.003%) to 94.899% when pulling 42a780a on giodamelio:order-extra-newlines into d9605a0 on benmosher:master.

@coveralls
Copy link

coveralls commented Oct 16, 2016

Coverage Status

Coverage increased (+0.003%) to 94.899% when pulling eabec08 on giodamelio:order-extra-newlines into d9605a0 on benmosher:master.

@giodamelio
Copy link
Contributor Author

@jfmengels Just wanted to ping you and check on the status of this. I would love to get it merged if everything is in order.

@giodamelio
Copy link
Contributor Author

I just updated this to the current master, @benmosher, could you take a look at this?

@coveralls
Copy link

coveralls commented Nov 16, 2016

Coverage Status

Coverage increased (+0.003%) to 94.863% when pulling 5c1a3d1 on giodamelio:order-extra-newlines into bfdc2bb on benmosher:master.

@benmosher
Copy link
Member

benmosher commented Dec 15, 2016

@giodamelio: need @jfmengels to review, order is his baby 😄

@jfmengels
Copy link
Collaborator

jfmengels commented Jan 21, 2017

Hey @giodamelio!
First of all, sorry for not replying earlier... Totally dropped the ball there.
Second of all, thanks a lot, this looks really good :)

The only thing I would like to see changed, is the new option name. In my mind, newlines-between: "always-with-newlines" means the same thing as newlines-between: "always". Maybe newlines-between: "always-and-inside-groups" would be more explicit? What do you think?

(apart for this, this LGTM, and I'll fine with merging this)

Oh, you'll probably need to rebase, because the changelog has moved since you made the PR, and the section is now located inside a previous release description. If you don't know how to rebase, nevermind, I can fix this when merging, no problem.

@giodamelio
Copy link
Contributor Author

"always-and-inside-groups" sounds good to me. Fix incoming.

@coveralls
Copy link

coveralls commented Jan 21, 2017

Coverage Status

Coverage increased (+0.003%) to 94.912% when pulling 9507de9 on giodamelio:order-extra-newlines into ffc0205 on benmosher:master.

@giodamelio giodamelio changed the title Add 'always-with-newlines' value to order's newlines-between option to allow newlines inside import groups Add 'always-and-inside-groups' value to order's newlines-between option to allow newlines inside import groups Jan 21, 2017
@giodamelio
Copy link
Contributor Author

Should be all good to go.

@jfmengels jfmengels merged commit b939718 into import-js:master Jan 22, 2017
@jfmengels
Copy link
Collaborator

Thanks a lot @giodamelio! 🎉

@coveralls
Copy link

coveralls commented Jan 22, 2017

Coverage Status

Coverage increased (+0.003%) to 94.912% when pulling 9639f2e on giodamelio:order-extra-newlines into ffc0205 on benmosher:master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-1.3%) to 93.612% when pulling 9639f2e on giodamelio:order-extra-newlines into ffc0205 on benmosher:master.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage decreased (-1.3%) to 93.612% when pulling 9639f2e on giodamelio:order-extra-newlines into ffc0205 on benmosher: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.

4 participants