Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replace all instances of the Pipeline api with the PowerShell api #646

Closed
TylerLeonhardt opened this issue Mar 25, 2018 · 2 comments
Closed
Labels
Area-General Issue-Enhancement A feature request (enhancement). Up for Grabs Will shepherd PRs.

Comments

@TylerLeonhardt
Copy link
Member

As mentioned in #641, the Pipeline class is on the chopping block and was not included in PowerShell Standard.

We should replace all Pipeline class usages with the PowerShell class.

I think their APIs are pretty similar so the change is relatively straightforward so I'm making this as Up-for-Grabs

@TylerLeonhardt TylerLeonhardt added Issue-Enhancement A feature request (enhancement). Up for Grabs Will shepherd PRs. Area-General labels Mar 25, 2018
@dee-see
Copy link
Contributor

dee-see commented Oct 28, 2018

This was already done in 2.0.0 by #690

@TylerLeonhardt
Copy link
Member Author

Nice catch. Closing

TylerLeonhardt pushed a commit to TylerLeonhardt/PowerShellEditorServices that referenced this issue Feb 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-General Issue-Enhancement A feature request (enhancement). Up for Grabs Will shepherd PRs.
Projects
None yet
Development

No branches or pull requests

2 participants