-
-
Notifications
You must be signed in to change notification settings - Fork 474
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 sorter revamping - custom order #3177
Comments
Would love to have this improved such that we can replace the following prettier config:
|
yeah.... give us a way to do the grouping automatically |
The issue has been funded! I will start work in a week. |
@MatheusRoichman based on @Conaclos 'last message, he started to work on the feature today. Please refrain from asking "whens" or for ETAs. The feature will be ready when it's ready. You may not realise this, but these kinds of messages put pressure on the person, which is something I want to avoid here. Thank you for understanding |
I pledged support for this feature several months ago so I come back to check it periodically. I am SO excited to see we've met the funding goal! Best of luck @Conaclos, you've got this! 🙌 |
I use a plugin forked from original Trivago and we setup a simple grouping for: company, team, root folder, that goes below the node/external packages.
I am glad to hear that development of this feature has started. Thanks. |
Description
We recently published an RFC to improve the Biome import sorter.
This issue tracks the implementation of the RFC.
The main goal of this implementation is to:
export from
statementsWe will provide a
legacy
configuration to enable the old way of sorting imports.By disabling this configuration, the new system will be used.
Upvote & Fund
The text was updated successfully, but these errors were encountered: