redhat-developer / redhat-developer/vscode-java

Renaming the f method causes naming conflicts

Open
#3,616 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

upstream
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

1.select "k()"
2.click “Rename”
3. new name "m()"

public class A {
void m(Object m){
System.out.println("A");
}
}
class B extends A{
// rename k to m
void k(String m){
System.out.println("B");
}
void f(){
m("1");
}
}

result:

public class A {
void m(Object m){
System.out.println("A");
}
}
class B extends A{
// rename k to m
void m(String m){
System.out.println("B");
}
void f(){
m("1");
}
}

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue in Visual Studio Code 1.88 with JDK 17 and Java extension 1.29: rename k() to m() in the supplied A/B example. Inspect the Java extension's Rename action and compare the generated result with the expected method resolution. Done means renaming no longer creates the conflicting declaration shown in the report.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, vscode
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.