Skip to content

Comments

Add capabilities for incomingCalls and outgoingCalls to metamodel#1720

Open
andrewbraxton wants to merge 1 commit intomicrosoft:mainfrom
andrewbraxton:dev/metamodel-callhierarchy
Open

Add capabilities for incomingCalls and outgoingCalls to metamodel#1720
andrewbraxton wants to merge 1 commit intomicrosoft:mainfrom
andrewbraxton:dev/metamodel-callhierarchy

Conversation

@andrewbraxton
Copy link

'callHierarchy/incomingCalls' and 'callHierarchy/outgoingCalls' do not have their own capabilities, but do depend on the callHierarchyProvider capability.

@andrewbraxton
Copy link
Author

@microsoft-github-policy-service agree

@phanen
Copy link

phanen commented Feb 7, 2026

Similar case: typeHierarchy/supertypes, typeHierarchy/subtypes

@andrewbraxton andrewbraxton force-pushed the dev/metamodel-callhierarchy branch from df55cab to f47e9c2 Compare February 12, 2026 00:05
@andrewbraxton andrewbraxton force-pushed the dev/metamodel-callhierarchy branch from f47e9c2 to 8441cb7 Compare February 12, 2026 00:07
@vs-code-engineering vs-code-engineering bot added this to the February 2026 milestone Feb 17, 2026
@dbaeumer dbaeumer enabled auto-merge (squash) February 17, 2026 10:49
'callHierarchy/incomingCalls' and 'callHierarchy/outgoingCalls' do not
have their own capabilities, but do depend on the callHierarchyProvider
capability.
auto-merge was automatically disabled February 22, 2026 00:11

Head branch was pushed to by a user without write access

@andrewbraxton andrewbraxton force-pushed the dev/metamodel-callhierarchy branch from 3774bd9 to b728676 Compare February 22, 2026 00:11
@andrewbraxton
Copy link
Author

Rebasing on main because 'vscode-languageserver-node' status check was stuck

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants