Fix IDE0049 for object in System.Management.Automation. Part 1#25923
Conversation
|
/azp run PowerShell-Windows-Packaging-CI, PowerShell-CI-linux-packaging |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
|
@iSazonov can we merge? |
|
/azp run PowerShell-Windows-Packaging-CI, PowerShell-CI-linux-packaging |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
| /// be an enumerable, you can derive from <see cref="ValidateEnumeratedArgumentsAttribute"/> | ||
| /// which will take care of unrolling the enumerable and validate each element individually. | ||
| /// It is also recommended to override <see cref="System.Object.ToString"/> to return a readable string | ||
| /// It is also recommended to override <see cref="object.ToString"/> to return a readable string |
There was a problem hiding this comment.
The System.Object full name looks better and matches what is in the documentation. I think it's right. Can we change only the code but not the XML comments?
There was a problem hiding this comment.
We would need #pragma warning disable IDE0049 // Simplify Names which would surely look worse. The documentation appears to be built automatically from these comments.
There was a problem hiding this comment.
Generated docs look good.
IDE0049 for object in System.Management.AutomationIDE0049 for object in System.Management.Automation. Part 1
|
📣 Hey @@xtqqczze, how did we do? We would love to hear your feedback with the link below! 🗣️ 🔗 https://aka.ms/PSRepoFeedback |
https://learn.microsoft.com/dotnet/fundamentals/code-analysis/style-rules/ide0049
Contributes to: #25922.
This change was isolated from #25900 using a filtering script.