Uh oh!
There was an error while loading. Please reload this page.
Correct highlight of replaced variables/splats with braces - #984
Conversation
Carl Morris (msftrncs)
commented
Aug 1, 2019
I think I figured out what the check for a The detection for a |
Prevent adjustment of userCompletionText while finding userCompletion text
position when match contains `{` in CompletionText[1] if the
userCompletionText is not longer than 1 char, and preserve the splat sigil
at start of completions of type `Variable`.
Adjusting userCompletionText blindly led to ArgumentOutOfRangeException on
incorrectly braced splats on input `@?`.6dee015 to
70d0d34CompareI've amended the commit for this PR. |
Dongbo Wang (daxian-dbw)
commented
Sep 6, 2019
The correction for maintaining the sigil of the returned |
Carl Morris (msftrncs)
commented
Sep 7, 2019
Dongbo Wang (@daxian-dbw), you are right, I was so focused on the |
userCompletionTextinFindUserCompletionTextPositionwhen the match contains{in CompletionText[1] if theuserCompletionTextis not longer than 1 charVariable.Adjusting
userCompletionTextblindly led toArgumentOutOfRangeExceptionon incorrectly braced splats on input@?.Loss of the sigil of splats led to the splat sigil always being marked as replaced, and in situations where the PowerShell completion logic returned incorrect completions of splats with braces, led to a
ArgumentOutOfRangeException.Fix#983.