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

react-error-overlay not open up file in windows (vscode) #5307

Closed
sercangurbuz opened this issue Oct 5, 2018 · 3 comments
Closed

react-error-overlay not open up file in windows (vscode) #5307

sercangurbuz opened this issue Oct 5, 2018 · 3 comments
Milestone

Comments

@sercangurbuz
Copy link

Is this a bug report?

I hope so

Did you try recovering your dependencies?

Yes

Which terms did you search for in User Guide?

WINDOWS_FILE_NAME_WHITELIST ,windows,react-error-overlay

Environment

Windows10,vscode

Steps to Reproduce

  1. give runtime error in any component
  2. try to locate the file clicking the error on overlay expecting vscode to open up the relevant file

Expected Behavior

I expect vscode to bring up the file which error is thrown in.

Actual Behavior

Absolute file path sent from webpackdevClient is considered as insecure and stuck in regex check WINDOWS_FILE_NAME_WHITELIST in react-error-overlay project.

Reproducible Demo

Say that ,File path is like below
D:/Samples/new/src/App.js

is not valid according to regex /^[\p{L}0-9/.-_\]+$/u
@acdlite

but if you remove the partition specifier from path like below it works and open up the file

/Samples/new/src/App.js

or

^[a-zA-Z]:/[\p{L}0-9/.-_\]+$

this regex helps accepting the partition specifier

@gaearon
Copy link
Contributor

gaearon commented Oct 5, 2018

Send a PR please?

@Timer Timer added this to the 2.0.x milestone Oct 5, 2018
@kanitsharma
Copy link

@gaearon Is this up for grabs?

@Timer Timer modified the milestones: 2.0.x, 2.0.5 Oct 8, 2018
@gaearon
Copy link
Contributor

gaearon commented Oct 14, 2018

Fixed by #5431.

@gaearon gaearon closed this as completed Oct 14, 2018
@lock lock bot locked and limited conversation to collaborators Jan 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants