Enable and fix VSTHRD200 (Use "Async" suffix for async methods)
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Start by reading .editorconfig and then trace the async methods flagged after VSTHRD200 is enabled. Done means the analyzer is enabled and the affected methods use the required Async suffix; the issue does not identify specific tests or files beyond .editorconfig.
Written by the indexing model from the issue text.
Description
Tracking TODO in .editorconfig.
- Dominant language
- C#
- Stars
- 78
- Forks
- 44
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dotnet/interactive-window
-
dotnet/interactive-window#255 · 2 comments · 6 reactions · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
dotnet/interactive-window#241 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
dotnet/interactive-window#230 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
dotnet/interactive-window#184 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
dotnet/interactive-window#183 ·
All issues in dotnet/interactive-window
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·