Use Unicode Control Pictures for special characters in assertions#2734
Merged
Conversation
Replace \n, \r, \t etc. with visible Unicode glyphs (U+2400 block) in Expand-SpecialCharacters, reusing the existing C# implementation in [Pester.Formatter]::EscapeControlChars(). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…rs in tests Control pictures are 1-to-1 replacements (1 char -> 1 char), so the expanded diff index equals the original. Remove the second scan loop from Be.ps1 and Should-BeString.ps1. Use actual Unicode control picture characters in test expectations instead of [char]0x24XX expressions so the expected output is readable. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Member
Author
|
/azp run |
Contributor
|
Azure Pipelines successfully started running 1 pipeline(s). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #2732
Replace
\n,\r,\t,\0,\bescape sequences in assertion error messages with visible Unicode Control Pictures (U+2400 block):␊,␍,␉,␀,␈.This reuses the existing
[Pester.Formatter]::EscapeControlChars()C# implementation (added for #2561) instead of the PowerShell regex chain. The glyphs are single characters, making arrow markers in diff output align correctly without doubling positions.