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

File casing issue with rename #62797

Closed
ghost opened this issue Nov 8, 2018 · 2 comments
Closed

File casing issue with rename #62797

ghost opened this issue Nov 8, 2018 · 2 comments

Comments

@ghost
Copy link

ghost commented Nov 8, 2018

Issue Type: Bug

Moving from microsoft/TypeScript#28401

  • Test on windows in a project with no tsconfig.json.
  • a.ts: import { b } from "./B";
  • b.ts: export const b = 0;
  • Open just a.ts.
  • Rename b to bee.
  • Vscode will open a new tab B.ts.
  • Click on b.ts in the file explorer. Now b.ts and B.ts are open side-by-side.

Expected behavior:

There is no b.ts B.ts distinction on windows.

Actual behavior:

There is and we have two duplicate files.

VS Code version: Code - Insiders 1.29.0-insider (5438af1, 2018-11-07T01:01:54.305Z)
OS version: Windows_NT x64 10.0.17134

System Info
Item Value
CPUs Intel(R) Xeon(R) CPU E5-1620 v3 @ 3.50GHz (8 x 3492)
GPU Status 2d_canvas: enabled
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
rasterization: unavailable_software
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
Memory (System) 15.91GB (9.21GB free)
Process Argv .
Screen Reader no
VM 0%
Extensions: none
@vscodebot vscodebot bot added the insiders label Nov 8, 2018
@vscodebot
Copy link

vscodebot bot commented Nov 8, 2018

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

@ghost
Copy link
Author

ghost commented Nov 8, 2018

Duplicate of #12448

@ghost ghost closed this as completed Nov 8, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Dec 23, 2018
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

0 participants