Enabling String and FileInfo Objects To Be Piped To Include Function

[UberDoodles]

Description

You can now do this :

$("File1.ps1","File2.ps1") | Include
Get-ChildItem | Include

Related Issue

#289

Motivation and Context

Allows users to write slightly more concise code, rather than writing for loops.

How Has This Been Tested?

New Pester tests have been added to verify that it can accept pipeline input both in the form of strings and FileInfo objects.

I also manually tested that it was backwards compatible, and could still work with the fileNamePathToInclude parameter.

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[devblackops]

Test-Path will return $true/$false so no need for the $null check.

If Test-Path returns $false, you're checking if that doesn't equal $null, which it doesn't, so the assert passes when it shouldn't if the function doesn't actually exist.

You can test this by putting in a bogus function name like so:

Assert (Test-Path 'Function:\BogusFunction') 'BogusFunction is not accessible'

Assert ($(Test-Path 'Function:\BogusFunction') -ne $null) 'BogusFunction  is not accessible'

Assert (Test-Path ...) will be fine.

[UberDoodles]

Yeah... not sure what I was thinking when I wrote that. I'm guessing I intended to write "-ne $false". Should have tested my test.

Thanks; I'll get it corrected.

[UberDoodles]

Pushed the fix now :)