Workspace treats c:\Users\ as different from file:///c:/Users/
Reported by
dyso...@gmail.com,
Jan 4 2018
|
|||
Issue descriptionDevTools failed to link network resource to filesystem. Platform: Windows Chrome version: 63.0.3239.132 (Official Build) (64-bit) What are the details of your project? - Source code (if any): https://github.com/dienluong/mv-js - HTTP server: node Assets failed to link (or incorrectly linked): 1. file:///C:/Users/dluong/Documents/dev/mv-js/... 2. C:\Users\dluong\Documents/dev/ms-js/... Workspace considers these two paths as different. I added folder file:///C:/Users/dluong/Documents/dev/mv-js to the Workspace using the + icon in "Filesystem" tab. The attached screenshot shows the project loaded in the WorkSpace, with two mvApp.js loaded. They are the exact same file on the file system but Workspace seems to treat them as distinct files. I ran: node_modules\.bin\mocha --inspect-brk test/mvApp.spec.js Then, I used DevTools to connect to NodeJS. Stepping through the execution works but breakpoints set in any source files added to the Workspace were never hit. (If I hover the cursor over to the files, the tooltip would show "file:///C:/Users/..."). While stepping through the execution, DevTools would load the SAME file but as "C:\Users\...". If I set breakpoints in that file, the breakpoints would work. So it seems WorkSpace does not realize that those are the same files!
,
Jan 9 2018
,
Dec 8
Workspaces 2.0 is imperfect and there's no feasible way to make it work for everybody. Archiving since we currently don't have resources to allocate towards improving Workspaces story. |
|||
►
Sign in to add a comment |
|||
Comment 1 by sc00335...@techmahindra.com
, Jan 5 2018