-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Import order rule #1971
Comments
That's because those paths are in different groups. You can configure the rule like this and play with how the groups are combined or separated. |
If I might be honest with you I couldn't understand much the usage and how to accomplish what I want with that config. |
Specifying the groups, and mixing |
It worked like this:
Thank you very much @ljharb |
I'm sorry, I just noticed it didn't work, it's still putting a new line on local imports if it's in a different folder (group). |
Try |
It worked, thank you very much @ljharb |
Is there a rule that won't allow local imports to be mixed with library imports? It would require an empty line between them, for example:
wrong:
wrong:
correct:
I want to group libraries import on top and local imports bellow with a space between them.
I tried setting the rule to
always
fornewlines-between
but it's adding a line betweenbiz
andboz
as well.The text was updated successfully, but these errors were encountered: