You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
isidorn opened this issue
Feb 25, 2020
· 2 comments
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesverifiedVerification succeeded
Notice how the range highlight in the editor is 1 character shorter than it should be. WHile the extracted result is correct
Upon looking at the mock debug implementation it seems like Mock debug incorectly returns a Range shorter by 1. And it seems like vscode properly shows this in the higlighted background, however the result extraction takes 1 character too much.
Contrast is not so strong but this picture shows the issue. y in funcitonlaity is not highlighted, while funcitonlaity is extracted as the result.
The text was updated successfully, but these errors were encountered:
Great find (because of the weak contrast of the selection color I did not notice the selection being off-by-one).
Please note: the fix is both in VS Code and Mock Debug.
weinand
added a commit
to microsoft/vscode-mock-debug
that referenced
this issue
Feb 26, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesverifiedVerification succeeded
Refs: #91268
Upon looking at the mock debug implementation it seems like Mock debug incorectly returns a Range shorter by 1. And it seems like vscode properly shows this in the higlighted background, however the result extraction takes 1 character too much.
Contrast is not so strong but this picture shows the issue.
y
infuncitonlaity
is not highlighted, while funcitonlaity is extracted as the result.The text was updated successfully, but these errors were encountered: