dotnet/roslyn

C# Text Editor: Options to sort fields, properties and methods

Open

#71,930 opened on Feb 2, 2024

View on GitHub
 (0 comments) (1 reaction) (0 assignees)C# (4,257 forks)batch import
Area-IDEhelp wanted

Repository metrics

Stars
 (20,414 stars)
PR merge metrics
 (Avg merge 6d 17h) (256 merged PRs in 30d)

Description

This issue has been moved from a ticket on Developer Community.

It would be nice for Visual Studio to implement a feature which allows for the IDE to sort written code (like fields, properties and methods) in a predefined order. I know that there are already paid extensions out there like ReSharper but they make the whole IDE really slow.

When looking at the products from JetBrains it is possible to describe what the code should be sorted by. For example if the fields and properties should be first sorted by name and then the access modifiers or vice versa.

Here's an image of their settings: image.png

Original Comments

Feedback Bot on 11/20/2023, 09:21 PM:

(private comment, text removed)

Contributor guide

Research direction
Investigate the existing Roslyn codebase for code analysis and refactoring APIs that could support sorting fields, properties, and methods. Look at how other features like 'Sort Usings' are implemented. Design a new code action or analyzer that provides sorting options based on access modifiers, names, etc.
Tech stack
csharp
Domain
developer experiencetooling
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
C#RoslynVisual Studio SDK
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30