-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[Linter] Update files with respect to sort-imports
rule
#18598
Conversation
Thank you for your contribution bzhang0! We will review the pull request and get back to you soon. |
Hi @bzhang0, Thanks a lot for these changes! While it is good to do this change and sort imports inside the plugin source code, it does not solve #9252 yet. To do so, the PR will need to add this new behavior as part of the plugin rules list. Once this is done, all imports in all packages across the repository can be sorted to satisfy the rule. Please use |
Oh, I see! I assumed putting the rule in the eslint's I will have these changes fixed. Thanks for letting me know! |
I'm getting an error when trying to call The error occurs on
These files all exist within my subdirectory. Any idea what the issue could be? |
This pull request is protected by Check Enforcer. What is Check Enforcer?Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass. Why am I getting this message?You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged. What should I do now?If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows: What if I am onboarding a new service?Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment: |
Hey @bzhang0, consider running |
At long last, all
Let me know if I'm missing something! |
@bzhang0 did you try |
I will try this! |
@bzhang0 Since this rule impacts almost every package this PR is becoming too large to manage reviews. We recommend breaking it into smaller ones in phases
Sorry for the trouble @bzhang0 ! Hopefully you just need to |
Will do! Just to clarify, you want me to do the following?
additionally, I will merge Azure:main and resolve respective conflicts. |
Closing this as we will have separate PRs for packages |
This solves #9252. This PR is an update from a past PR, #18567.
What's new?
sort-imports
rule into./common/tools/eslint-plugin-azure-sdk/.eslintrc.json
rush rebuild
andrush lint
.I used the default settings for
sort-imports
, so if there should be changes to the rule settings, please let me know!