Tests targeting NetStandard due to conflicting types
- Dominant language
- C#
- Stars
- 20.7k
- Forks
- 4.3k
- PR merge metrics
- PR metrics pending
Description
These are some of the test types targeting `netstandard2.0` due to conflicting types. This is typically because the test targeted and older TFM where it had to provide source for a new type (for example an attribute). This can typically be cleaned up with a small bit of work:
Types:
- [ ] RefEscapingTests
- [ ] RefFieldTests
- [ ] RawInterpolationTests
- [ ] UninitializedNonNullableFieldTests
- [ ] IndexAndRangeTests
- [ ] LambdaTests
- [ ] LocalFunctionTests
- [ ] Utf8StringsLiteralsTests
- [ ] InterceptorsTests
- [ ] InterpolationTests
- [ ] FieldKeywordTests
- [ ] FirstClassSpanTests
- [ ] PatternMatchingTests_ListPatterns
- [ ] PatternMatchingTests4
- [ ] PatternMatchingTests5
- [ ] ReadOnlyStruct
- [ ] RefStructInterfacesTests
- [ ] ExtensionTests
Contributor guide
Research direction
Inspect the test project targeting settings and the listed test types, starting with why each still targets netstandard2.0. Work through the checklist and verify that each type no longer needs the older target or conflicting source; done means all listed items are resolved and the tests still pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- build-system, testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100