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

The front part of file paths on debug console are ignored #26309

Closed
dyong0 opened this issue May 9, 2017 · 2 comments
Closed

The front part of file paths on debug console are ignored #26309

dyong0 opened this issue May 9, 2017 · 2 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug *duplicate Issue identified as a duplicate of another issue(s)

Comments

@dyong0
Copy link

dyong0 commented May 9, 2017

  • VSCode Version: Code 1.12.1 (f6868fc, 2017-05-04T21:40:39.245Z)
  • OS Version: Linux x64 4.8.0-51-generic
  • Extensions:
Extension Author Version
code-settings-sync Shan 2.7.0
theme-dracula dracula-theme 1.15.0
tslint eg2 0.14.0

Steps to Reproduce:

  1. Run Start Debug, which runs mocha tests and prints test results with file paths on DEBUG CONSOLE
    screenshot from 2017-05-09 21-31-48
  2. Click a file path on DEBUG CONSOLE
    screenshot from 2017-05-09 21-40-12

I think that the parser should search words backward after detecting a file path in debug console, so that it doesn't ignore the front part of relative paths. Currently the parser seems to only look forward when searching using regular expressions.

@isidorn
Copy link
Contributor

isidorn commented May 9, 2017

I think it is fine when clicking on a false positive that it shows up with an error.
However what I do not understand is why our link detector does not detect src/ as part of the link. Thus forwarding to @michelkaporin

@isidorn isidorn added the bug Issue identified by VS Code Team member as probable bug label May 9, 2017
@isidorn isidorn removed their assignment May 9, 2017
@michelkaporin
Copy link
Contributor

michelkaporin commented May 9, 2017

This is a duplicate of #15760, and has been fixed in #24451. Insiders has its fix already, @dyong0.

@michelkaporin michelkaporin added the *duplicate Issue identified as a duplicate of another issue(s) label May 9, 2017
@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 *duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

3 participants