Make prompt colors configurable

[dkaszews]

Prerequisites

• Existing Issue: Search the existing issues for this repository. If there is an issue that fits your needs do not file a new one. Subscribe, react, or comment on that issue instead.
• Descriptive Title: Write the title for this issue as a short synopsis. If possible, provide context. For example, "Document new Get-Foo cmdlet" instead of "New cmdlet."

Summary

PowerShell/PowerShell#18003 introduces new properties to $PSStyle that control how -Confirm prompt is rendered:

$PSStyle.Prompt.Caption
$PSStyle.Prompt.Message
$PSStyle.Prompt.Help
$PSStyle.Prompt.ChoiceDefault
$PSStyle.Prompt.ChoiceOther
$PSStyle.Prompt.ChoiceHelp

Details

The documentation should explain which property controls which part of the confirm prompt. In the example below:

$PSStyle.Prompt.Caption = $PSStyle.Background.Red  # First line
$PSStyle.Prompt.Message = $PSStyle.Foreground.BrightBlack  # Other lines
$PSStyle.Prompt.Help = $PSStyle.Foreground.Purple  # "default is"
$PSStyle.Prompt.ChoiceDefault = $PSStyle.Foreground.Purple  # First choice
$PSStyle.Prompt.ChoiceOther = $PSStyle.Foreground.Blue  # Other choices
$PSStyle.Prompt.ChoiceHelp = $PSStyle.Foreground.Green  # Choice "[?] Help"

An image with rectangles and arrows deliminating each section may be clearer than trying to match colors.

Articles

• reference/7.4/Microsoft.PowerShell.Core/About/about_CommonParameters.md, section -Confirm

Related Source Pull Requests

• Make prompt colors configurable PowerShell/PowerShell#18003

Related Source Issues

• Prompt colors not configurable, not visible on white background PowerShell/PowerShell#17961

[sdwheeler]

Closing this issue for now. We can reopen if the PR ever moves forward.

[dkaszews]

@sdwheeler With all due respect, what? The PR has been approved for over 3 years now, just waiting for any maintainer to click "merge". And instead of reviewing it and merging, you just close the issue, pretending it doesn't exist?

[sdwheeler]

@sdwheeler With all due respect, what? The PR has been approved for over 3 years now, just waiting for any maintainer to click "merge". And instead of reviewing it and merging, you just close the issue, pretending it doesn't exist?

I understand your frustration. I want the change you made. As I said, we can reopen when the code is merged.

[dkaszews]

@sdwheeler I just don't understand the logic of "wanting the change" but closing an issue instead of merging it. And why would you reopen an issue after the fix is merged so there is no issue anymore? If it needs someone else's attention, then it would be more productive putting it in front of them.

[sdwheeler]

@dkaszews This is the docs issue, not the code issue.

[dkaszews]

@sdwheeler My sincere apologies, I did not notice this was the docs repo which lead me to confusion and, yes, frustration.

Still, I would appreciate if you could give the code issue or PR a nudge, a comment from you or an internal message to anyone who participated last year could probably help see it through.