-
Notifications
You must be signed in to change notification settings - Fork 34.3k
Closed
Labels
javascriptJavaScript support issuesJavaScript support issuestypescriptTypescript support issuesTypescript support issuesupstreamIssue identified as 'upstream' component related (exists outside of VS Code)Issue identified as 'upstream' component related (exists outside of VS Code)
Description
Issue Type: Bug
If you select a named export with your cursor and choose "Move to new file" the export is moved and named imports are updated but imports using import * as myExports from 'myModule;'
don't get updated. I would expect a new named import to be added with the correct path to the new module and all the references to myExports.export
to be changed to the new import.
VS Code version: Code - Insiders 1.24.0-insider (0853749, 2018-05-31T05:10:58.506Z)
OS version: Darwin x64 17.5.0
System Info
Item | Value |
---|---|
CPUs | Intel(R) Core(TM) i7-3720QM CPU @ 2.60GHz (8 x 2600) |
GPU Status | 2d_canvas: unavailable_software flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on native_gpu_memory_buffers: enabled rasterization: unavailable_software video_decode: enabled video_encode: enabled vpx_decode: enabled webgl: enabled webgl2: enabled |
Load (avg) | 2, 3, 3 |
Memory (System) | 16.00GB (0.82GB free) |
Process Argv | /Applications/Visual Studio Code - Insiders.app/Contents/MacOS/Electron -psn_0_1122578 |
Screen Reader | no |
VM | 0% |
Metadata
Metadata
Assignees
Labels
javascriptJavaScript support issuesJavaScript support issuestypescriptTypescript support issuesTypescript support issuesupstreamIssue identified as 'upstream' component related (exists outside of VS Code)Issue identified as 'upstream' component related (exists outside of VS Code)