Skip to content
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

Clicking string in debugger get stuck with "unexpected identifier" error #10666

Closed
georgeedwards opened this issue Aug 18, 2016 · 2 comments
Closed
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues verified Verification succeeded
Milestone

Comments

@georgeedwards
Copy link

  • VSCode Version: 1.4.0
  • OS Version: Windows 10 pro

Steps to Reproduce:

  1. Debug an (in my case nodeJS) app and trigger a breakpoint
  2. Click on a string value in Variables > Local, such that you can edit or select it's contents
  3. Click away having not made any modification to the variables content
  4. Get irritated by the unexpected identifier error that stops you doing anything else ...

enter image description here

@alexdima
Copy link
Member

fyi @weinand

@weinand weinand assigned weinand and unassigned isidorn Aug 19, 2016
@weinand weinand added debug Debug viewlet, configurations, breakpoints, adapter issues bug Issue identified by VS Code Team member as probable bug labels Aug 19, 2016
@weinand
Copy link
Contributor

weinand commented Aug 19, 2016

This problem occurs if the value of a string contains a string delimiter (double quote character):

var a = "hello\"world";   // error
var b = 'hello\'world';   // OK
var c = 'hello\"world';   // error

@weinand weinand added this to the August 2016 milestone Aug 19, 2016
@jrieken jrieken added the verified Verification succeeded label Sep 1, 2016
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

5 participants