microsoft / microsoft/vscode-java-pack

"Show Call Hierarchy" on interface method shows calls to return type's constructors instead

Open
#757 1 comment 0 reactions 1 assignee View on GitHub

@testforstephen is already working on this.

Since Dec 3, 2021.

ai-triaged bug
Dominant language
TypeScript
Stars
352
Forks
166
Avg merge
17h 47m
Merged PRs (30d)
32

Description

Environment:

Version: 1.61.0-insider (user setup)
Commit: 0c83ca1ced83259971d80890d93abbe19cbfc992
Date: 2021-09-15T05:16:32.507Z
Electron: 13.1.8
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.19042

  • VS Code Version: 1.61.0-insider (user setup)
  • Extension Version: 0.18.5
  • JDK Type & Version: 11.0.10+9
  • OS Type & Version: Windows 10 Pro (20H2 19042.1165 Windows Feature Experience Pack 120.2212.3530.0)

Step to Reproduce:
Given a java interface, like the one below

package mypackage;

public interface IMyService {
    Long doService(MyDTO dto, MyOtherDTO other) throws MyServiceException;
}

Right-click doService method, and "Show Call Hierarchy" (Shift+Alt+H).

Expected Behavior:
I was expecting a list of calls to doService, either over a reference to the given interface or subinterface thereof, or any implementing class, or subclass thereof.

Actual Behavior:

The "References" view appears with a very very long list of method calls, aptly rooted at doService(MyDTO dto, MyOtherDTO other), but the calls are actually those of new Long(...).

Contributor guide

No contributing guide indexed for this repository

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.