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
Since prettier typically ignores the order of import statements, we run into merge conflicts if some developers are using IntelliJ based IDEs, which handle import order automatically and others VSCode, which does not (out of the box).
VSCode users can configure similar behaviour in settings json with "editor.codeActionsOnSave": { "source.organizeImports": true }
For an IDE independent solution, we could use prettier-plugin-organize-imports.
I opened a PR for that change, but since this will cause changes in almost every file, we should make sure that every other PR is merged before a project wide run-through of the organize-imports plugin.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Since prettier typically ignores the order of import statements, we run into merge conflicts if some developers are using IntelliJ based IDEs, which handle import order automatically and others VSCode, which does not (out of the box).
VSCode users can configure similar behaviour in settings json with
"editor.codeActionsOnSave": { "source.organizeImports": true }
For an IDE independent solution, we could use prettier-plugin-organize-imports.
I opened a PR for that change, but since this will cause changes in almost every file, we should make sure that every other PR is merged before a project wide run-through of the organize-imports plugin.
Beta Was this translation helpful? Give feedback.
All reactions