The naming suggestions for parameters should include names appearing for matching types in overloads. For example, the following parameters are all representing the same data, but appearing with three different names:
sessionName:
|
private RunCompilationResult? RunServerCompilation(TextWriter textWriter, List<string> arguments, BuildPaths buildPaths, string libDirectory, string sessionName, string keepAlive) |
sessionKey:
pipeName:
Suggesting parameter names from overloads according to matching types (while accounting for the Async Pattern and Template Method Pattern naming conventions) would help avoid these mismatches.
Related to #52505
The naming suggestions for parameters should include names appearing for matching types in overloads. For example, the following parameters are all representing the same data, but appearing with three different names:
sessionName:roslyn/src/Compilers/Shared/BuildClient.cs
Line 212 in 5509233
sessionKey:roslyn/src/Compilers/Shared/BuildClient.cs
Line 272 in 5509233
pipeName:roslyn/src/Compilers/Shared/BuildClient.cs
Line 284 in 5509233
Suggesting parameter names from overloads according to matching types (while accounting for the Async Pattern and Template Method Pattern naming conventions) would help avoid these mismatches.
Related to #52505