Skip to content

Fix evaluation of prompt function output to remove unneeded "PS>" #479

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

Merged
merged 1 commit into from
May 31, 2017

Conversation

daviwil
Copy link
Contributor

@daviwil daviwil commented May 31, 2017

This change fixes an issue in the integrated console where the result of
a user's custom prompt function would not be interpreted correctly,
causing the default prompt string of "PS>" to be written out when it
wasn't needed. The fix is to expect a PSObject result rather than
object so that we can evaluate the inner object's type correctly.

Resolves PowerShell/vscode-powershell#808.

This change fixes an issue in the integrated console where the result of
a user's custom prompt function would not be interpreted correctly,
causing the default prompt string of "PS>" to be written out when it
wasn't needed.  The fix is to expect a PSObject result rather than
object so that we can evaluate the inner object's type correctly.

Resolves PowerShell/vscode-powershell#808.
@daviwil daviwil added this to the 1.2.1 milestone May 31, 2017
@daviwil daviwil merged commit c03b7fb into PowerShell:master May 31, 2017
@daviwil daviwil deleted the fix-vsc-808 branch May 31, 2017 22:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

PS> being added to custom prompts for some users
2 participants