Presently, almost every cmdlet in the module that supports attributes from the pipeline, doesn't use a process statement,
This is an issue because to iterate through each item, we would need a for each statement, increasing inefficiency.
I have no issue re-writing some of these modules but, I need to make sure that the changes arent breaking, and that I can pass attributes back in the $Return variable for each object in the pipeline.
This will also need to happen as part of the improvement to the Reporting functionality to support faster user moves from on-prem to the cloud.
Presently, I am supressing the warnings in PSScriptAnalyzer with the following code.
[Diagnostics.CodeAnalysis.SuppressMessageAttribute('PSUseProcessBlockForPipelineCommand', '', Scope='Function')]
Presently, almost every cmdlet in the module that supports attributes from the pipeline, doesn't use a process statement,
This is an issue because to iterate through each item, we would need a for each statement, increasing inefficiency.
I have no issue re-writing some of these modules but, I need to make sure that the changes arent breaking, and that I can pass attributes back in the $Return variable for each object in the pipeline.
This will also need to happen as part of the improvement to the Reporting functionality to support faster user moves from on-prem to the cloud.
Presently, I am supressing the warnings in PSScriptAnalyzer with the following code.
[Diagnostics.CodeAnalysis.SuppressMessageAttribute('PSUseProcessBlockForPipelineCommand', '', Scope='Function')]