RCS1155 in LINQ to SQL
Open
Area-Analyzers
Bug
- Dominant language
- C#
- Stars
- 3.5k
- Forks
- 294
- Avg merge
- 2h 30m
- Merged PRs (30d)
- 4
Description
Is it possible for you to detect when the statements causing this are being used in LINQ to SQL and do not flag them in those cases? Oracle Data Provider for .net does not support three parameter overload of string.Equals (at least on the version I am using).
Contributor guide
Research direction
Start by locating the RCS1155 analyzer and its tests, then inspect how LINQ to SQL calls are represented. Done means the analyzer avoids flagging the affected string.Equals usage in LINQ to SQL while retaining the diagnostic elsewhere, with tests covering both cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100