dotnet/roslyn

Refactoring Extract an Interface should include xml comments

Open

#30,948 opened on Nov 4, 2018

View on GitHub
 (3 comments) (4 reactions) (0 assignees)C# (4,257 forks)batch import
Area-IDEDeveloper CommunityFeature - Extract Interfacehelp 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 https://developercommunity.visualstudio.com/content/idea/358771/refactoring-extract-an-interface-should-include-xm.html VSTS ticketId: 706627 These are the original issue comments:

Fiona Niu[MSFT] on 10/16/2018, 07:19 PM (18 days ago): Thank you for taking the time to provide your suggestion. We will do some preliminary checks to make sure we can proceed further. You will hear from us in about a week on our next steps. Kendra Havens [MSFT] on 10/31/2018, 03:26 PM (3 days ago): Your suggestion has been queued up for prioritization. Feature suggestions are prioritized based on the value to our broader developer community and the product roadmap. We may not be able to pursue this one immediately, but we will continue to monitor it up to 90 days for community input

Contributor guide

Research direction
Examine the Extract Interface refactoring implementation in Roslyn, focusing on how XML comments are currently omitted, and consider adding them similar to how other refactorings preserve comments.
Tech stack
csharp
Domain
developer experience
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.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C#GitRoslyn
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30