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
In some of my projects there are special files (recognisable by their names) that always import certain base classes. I'd like to always have those at the top as a kind of header, but split into other groups in regular files.
I'd be helpful if one could create multiple configurations in the import-sorter.json file, which are selected based on regex matching of the file path. Possibly by optionally wrapping the configuration in a top-level array and adding an include option similar to the current exclude.
The alternative would be to change the tsImportSorter.configuration.configurationFileName setting in VSCode depending on those patterns, but microsoft/vscode#35350 might take some time.
The text was updated successfully, but these errors were encountered:
None of those are helpful in this specific context.
No, those files are not in separate directories, that's why I spoke of recognition by name pattern, not folder.
Not maintaining them manually is one of the biggest reasons to do it automatically, because those files specifically tend to have a huge amount of imports.
As mentioned before, no, those import appear elsewhere and should not be grouped separately there.
In some of my projects there are special files (recognisable by their names) that always import certain base classes. I'd like to always have those at the top as a kind of header, but split into other groups in regular files.
I'd be helpful if one could create multiple configurations in the
import-sorter.json
file, which are selected based on regex matching of the file path. Possibly by optionally wrapping the configuration in a top-level array and adding aninclude
option similar to the currentexclude
.The alternative would be to change the
tsImportSorter.configuration.configurationFileName
setting in VSCode depending on those patterns, but microsoft/vscode#35350 might take some time.The text was updated successfully, but these errors were encountered: