While I am preparing my next article, I wanted to share with you this short post with an excellent configuration for your React or React Native app...
For further actions, you may consider blocking this person and/or reporting abuse
Thanks for this. My config is pretty much the same as yours except for groups
This gives me one more group of import statements for all files that are imports from
../
and./
filesYes, that's great. Thanks!
Thanks for the config, I figured it out how to group react and react-native import first with this pattern
How do I also include "expo" in that pattern?
excellent. now i only need to figure out how to write that in YAML..
import/order
works great until it hits code like:It will simply ignore
{ b, c, a }
sorting. I have tried coupling it withsort-import
but they are conflicting.So, in the end, I will probably resort to simple-import-sort which does both, grouping and sorting in groups as well as import members.
Thanks for pointing to eslint-plugin-simple-import-sort simple to configure and worked great for me.
I have been doing this manually😅. I feel stupid but now I'm not
Glad it was helpful!.
I really like the ESLint approach. FWIW, I recently wrote an article extolling the benefits of sorting your code in many other areas of the application as well:
dev.to/bytebodger/sorting-code-alp...
Does anyone experiences wrong regex behaviour with groupPath pattern?
Can you specify your problem?
this is great although not sure how strict the alphabetic sort is. seems to be a little spotty
i wonder if this plugin also support non default imports (i.e. { a, b, c } from "x")
Thank you for your effort!
I have searched this formatting option after reading your post and i have a wonder for option "pathGroupsExcludedImportTypes".
I read many times your post and eslint-import-order.md (github.com/benmosher/eslint-plugin...) but i don't understand.
What kind of situations should I use this for?
Could you please explain in more detail?
Thank you!
After several tries and error. my guess is that those import types included in "pathGroupsExcludedImportTypes" (default: ["builtin", "external"]) won't be working on "pathGroups" configuration. So by default, the pathGroups won't be working in "builtin" and "external".
Basically he overwritten the default value of pathGroupsExcludedImportTypes to "react" , which is none of the valid import type. Therefore, "pathGroups" will work on all import types in this case.
You simply saved my day!
And i thought i am alone by doing this, thanks for your contribution 🙌
This is awesome.
How about if we use for Angular? Btw have you been able to use any ext that can auto reorder imports based on the eslint rule?
To use for Angular, I think you should use a tool like typescript-eslint for ESLint support Typescript and then use the plugin as I mentioned in the article. In theory, this should work, but I didn't try myself.
Regarding extensions to help you auto-reorder, you have the ESLint extension. With the help of setting
editor.formatOnPaste": true
andeditor.formatOnSave": true
on the VS Code settings you should be able to sort automatically on save and paste using the ESLint rule.Sweet~ I didn't know that you could enforce import rules with ESLint!
Thanks for sharing, Martín
Thanks!
This is so nice!! thank you for sharing
This makes me wonder how much time I wasted sorting imports manually...