Enable the sort-imports eslint rule

[ramya-rao-a]

The sort-imports eslint rule is pretty helpful to manage imports. Having the imports sorted helps with code reviews as well when PRs introduces a large number of imports.

Code pointers for anyone wanting to fix this:

• Set up your dev env if you have not already
• ESLint Plugin source package

Unless there are only a couple of packages to fix, it would make pull request easier to managed if we do it in phases

1. First PR to add the rule to the plugin but treat violations as warnings
2. Then separate PRs for fixing errors reported by the linter rule in each package.
3. Once all of them are merged, another PR to change violations from warnings to error

[bzhang0]

Hello! Would we be adding sort-imports into the base config "rules" in .\common\tools\eslint-plugin-azure-sdk? Or does this pertain to all .eslintrc.json files within all subdirectories?

This is my first time contributing so I'm just trying to learn how the rules works and if there's anything else that needs to be tested/checked after this rule is added.

Thanks!

[ramya-rao-a]

The individual .eslintrc.json is to override any of the rules set in the common place i.e. in the plugin. So, you should go ahead and add it to the plugin first, run the linter for each package and fix the places where the rule fails

[kkreine]

Hi @ramya-rao-a, is this issue resolved, or is there further work to be done?

[github-actions]

Hi @ramya-rao-a, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.