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

Update paths not triggered on rename if you have never opened a js/ts file #51298

Closed
mjbvz opened this issue Jun 7, 2018 · 1 comment
Closed
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug javascript JavaScript support issues *out-of-scope Posted issue is not in scope of VS Code typescript Typescript support issues
Milestone

Comments

@mjbvz
Copy link
Collaborator

mjbvz commented Jun 7, 2018

Steps to Reproduce:

  1. Create an empty workspace with two ts files in it:

a.ts:

export const a = 1;

b.ts:

import { a } from './a';
console.log(a);
  1. Close all files and restart vscode.
  2. Without opening any ts file, use the explorer to rename a.ts to x.ts

Bug
No update paths prompt shown

@mjbvz mjbvz added the bug Issue identified by VS Code Team member as probable bug label Jun 7, 2018
@mjbvz mjbvz self-assigned this Jun 7, 2018
@mjbvz mjbvz added typescript Typescript support issues javascript JavaScript support issues labels Jun 7, 2018
@mjbvz mjbvz added this to the Backlog milestone Jan 23, 2020
@mjbvz mjbvz added the *out-of-scope Posted issue is not in scope of VS Code label Nov 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug javascript JavaScript support issues *out-of-scope Posted issue is not in scope of VS Code typescript Typescript support issues
Projects
None yet
Development

No branches or pull requests

2 participants
@mjbvz and others