Skip to content

Support seamless pipelining of related cmdlets #63

Closed
@danbelcher-MSFT

Description

@danbelcher-MSFT

Many related PowerShell cmdlets are designed to operate off of a common datatype in order to support pipelining, e.g.

Get-ChildItem .. | Remove-Item

So Get-ChildItem outputs a [System.IO.FileInfo] object and Remove-Item is designed to populate it's input either from a [System.IO.FileInfo] object or by explicit named parameter.

The cmdlets in this module should support a similar paradigm, so that related cmdlets can be seamlessly piped to each other, as PowerShell users would expect, e.g.

New-GitHubMilestone ... |
    Update-GitHubIssue -Issue 4 -PassThru |
    Update-GitHubIssue -Issue 10

In this example, the OwnerName, RepositoryName, and Milestone can be inferred based on the presence of the Milestone object in the pipeline.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementAn issue or pull request introducing new functionality to the project.help wantedAnyone in the community is welcome to do this worktechnical debtWork that was postponed by a previous change.up for grabsAnyone in the community is welcome to do this work

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions