You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm looking into removing the ESLint plugin we use on TS to sort/group imports, as using dprint to do this would be a lot faster and less noisy. But, for "reasons" we have files that need to import from the same module specifier more than once. While messing with imports to try and make sure that sorting was working, I noticed that reordering those duplicates didn't net a single output.
I'm not 100% sure how to sort between these, but eslint-plugin-simple-import-order seems to do it. At least in the examples below, I think the ordering is at least sort of clear; stick the namespace import before the declaration with named imports.
I think it may be sufficient to just put the namespace import before a named/default import, actually. If you're importing with names but twice, that's weird and probably pointless as those two could be merged.
Describe the bug
I'm looking into removing the ESLint plugin we use on TS to sort/group imports, as using dprint to do this would be a lot faster and less noisy. But, for "reasons" we have files that need to import from the same module specifier more than once. While messing with imports to try and make sure that sorting was working, I noticed that reordering those duplicates didn't net a single output.
I'm not 100% sure how to sort between these, but
eslint-plugin-simple-import-order
seems to do it. At least in the examples below, I think the ordering is at least sort of clear; stick the namespace import before the declaration with named imports.dprint-plugin-typescript version: 0.90.0
Input Code
Expected Output
Actual Output
The text was updated successfully, but these errors were encountered: