microsoft / microsoft/vscode-java-dependency
Wired behavior when moving node in Java Project
Open
Nobody has claimed this yet.
bug
upstream
- Dominant language
- TypeScript
- Stars
- 199
- Forks
- 105
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 27
Description
Moving node should trigger a refactoring, currently some wired behavior can be observed:
- The changed files are not auto saved
- Some referenced files contains errors. The errors will disappear after opening the file, or trigger a
save allaction
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named; start by locating the node-move and refactoring flow in the TypeScript VS Code extension and reproduce the two reported symptoms. Done means moving a Java project node saves changed files automatically and referenced-file errors clear without opening files or invoking Save All.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, typescript, vscode
- Domain
- developer-experience, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100