eslint-plugin-import-x icon indicating copy to clipboard operation
eslint-plugin-import-x copied to clipboard

Please clarify in readme the differences to eslint-plugin-import

Open darkgreentree opened this issue 9 months ago • 0 comments

I would like to see written in readme, at the beginning, in easy language for people that do not understand technical terms, what are the differences we should expect between this plugin eslint-plugin-import-x and eslint-plugin-import.

I have read your comments on other threads, and it is clear that this decision is still pending, but for now, I mean, what is the current situation? Is your plugin going to be updated from time to time to keep in sync with updates that may arrive in eslint-plugin-import? What process are you going to follow to evaluate the situation for each update that arrives in eslint-plugin-import? New features or only fixes are going to be ported to eslint-plugin-import-x? I understand that you are focusing on typescript and cleaning the house, but what else after that is going to guide the maintenance and eventually the addition of features?

As someone coming from eslint-plugin-import, I wonder if I should just rename the rules from import to import-x,

or maybe your plugin has already added or changed some rules and options along the way. Probably I don't need to compare the documentation for each rule in both plugins, but the information is not clear in readme.md. If in the future, your rules and options become different from what used to be, please consider informing that in the table of rules.

Thank you.

darkgreentree avatar May 18 '24 02:05 darkgreentree