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

Review call hierarchy api proposal #71098

Closed
1 task done
jrieken opened this issue Mar 25, 2019 · 3 comments
Closed
1 task done

Review call hierarchy api proposal #71098

jrieken opened this issue Mar 25, 2019 · 3 comments

Comments

@jrieken
Copy link
Member

jrieken commented Mar 25, 2019

Refs: #70231

Complexity: 2

Review the call hierarchy API proposal: https://github.com/Microsoft/vscode/blob/61c990fb6f1a7cdd7ff599156f2002b36b7b079f/src/vs/vscode.proposed.d.ts#L21-L68

@jrieken jrieken removed their assignment Mar 25, 2019
@jrieken jrieken added this to the March 2019 milestone Mar 25, 2019
@aeschli
Copy link
Contributor

aeschli commented Mar 26, 2019

@jrieken in the returned [CallHierarchyItem, Location[]][], wouldn't the locations always be inside the CallHierarchyItem? Does it have to be a Location then, or is Range[] enough?

@jrieken
Copy link
Member Author

jrieken commented Mar 26, 2019

Yeah, they are always inside "a" call hierarchy item, e.g the item making the call so either items from the returned tuples or when the arguments. I have no strong feelings, there are more arguments in the LSP item: microsoft/vscode-languageserver-node#420 (comment)

@aeschli aeschli removed their assignment Mar 27, 2019
@aeschli
Copy link
Contributor

aeschli commented Mar 27, 2019

Discussed with @jrieken. We wrote down a new proposal in #70231 (comment)

@aeschli aeschli closed this as completed Mar 27, 2019
@vscodebot vscodebot bot locked and limited conversation to collaborators May 11, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants