You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Similar code style rule already exists (dotnet_sort_system_directives_first), but there is no analyzer (see #77024).
This is confusing as it is listed under IDE0055 in MS docs, and looks just like other code style rules which do have analyzers (allowing build enforcement and IDE warning/error markings).
Ideally, also introduce a new code style rule (dotnet_sort_imports) which enables sorted usings independent of System usings order.
Any kind of analyzer that checks for sorted usings would be super useful for avoiding constant code changes from devs who haven't enabled Code Cleanup on save, and would make it easier to enforce it on cli builds too.
Brief description:
Similar code style rule already exists (dotnet_sort_system_directives_first), but there is no analyzer (see #77024).
This is confusing as it is listed under IDE0055 in MS docs, and looks just like other code style rules which do have analyzers (allowing build enforcement and IDE warning/error markings).
Ideally, also introduce a new code style rule (dotnet_sort_imports) which enables sorted usings independent of System usings order.
Any kind of analyzer that checks for sorted usings would be super useful for avoiding constant code changes from devs who haven't enabled Code Cleanup on save, and would make it easier to enforce it on cli builds too.
Languages applicable:
Both, or C#-only
Code example that the analyzer should report:
or
Additional information:
Any more additional information you would like to add.
Documentation requirements:
When this analyzer is implemented, it must be documented by following the steps at Documentation for IDE CodeStyle analyzers.
The text was updated successfully, but these errors were encountered: