C#: Re-factor order of usings. #13995
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
michaelnebel
force-pushed
the
csharp/refactorimports
branch
2 times, most recently
from
ee2944d to
dd5a9fd
Compare
michaelnebel
force-pushed
the
csharp/refactorimports
branch
from
dd5a9fd to
864f60f
Compare
michaelnebel
added
the
no-change-note-required
hvitved
approved these changes
Aug 21, 2023
That is a really good question (I didn't use any when doing the rearrangement)! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In this PR we introduce the following standard for
usingstatements in our C# extractor source code files.The order is
System*(the standard library).Microsoft.CodeAnalysis).Semmle*(out own namespaces), starting withSemmle.Util*(the remaining is in alphabetical order)Unit test projects follows the same pattern except that the first using statement is
using Xunit.