redhat-developer / redhat-developer/vscode-java
Bug: Renaming fields causes naming conflicts between fields, missing check warnings
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 546
- Avg merge
- 20h 1m
- Merged PRs (30d)
- 11
Description
[provide a description of the issue]
Environment
Operating System: Windows11
JDK version: 17
Visual Studio Code version: 1.88
Java extension version: 1.29
Steps To Reproduce
- renaming 'fieldToRename' to 'newField'
- Syntax error
Current Result：
Expected Result： When naming conflicts occur between fields, a warning should be given
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 source file, test, or entry point is named. Reproduce the field rename in VS Code using the stated Windows 11, JDK 17, VS Code 1.88, and Java extension 1.29 environment, then trace the rename behavior responsible for the syntax error. Done means a naming conflict between fields produces a warning instead of the reported result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100