Closed Stuart-Wilcox closed 8 months ago
That's awesome, I've been wanting something similar for a while now!
Okay, played around with it a bit and pushed some of my changes to get things working. Notably:
template
word which would fail).Location.create
wants a URI in the form of a string, so toString()
was the right call after all. Sorry for the doubt here! It was tricky to figure out without the type signatures :ProotPath
. Now it parses from a still-deprecated-but-slightly-less-so rootUri
! (We really need to sync this repo with the last 5 years' worth of changes from upstream...)@Stuart-Wilcox if these changes look good to you, I'll push the big green button :).
Thanks for adding those changes, it all looks good to me!
Thank you for the contribution!!
Motivation
My teams makes significant use of the ADO Pipeline template paradigm and has many template references all over our pipeline definitions.
One of the most annoying things about this pattern is that when navigating around in VSCode, you need to select the full template path, copy it, and CTRL+P to open it in a new tab. Thus the motivation here is to have a seamless experience like in JS/TS where using F12 (or context clicking and selecting "Go To Definition") which takes you right to the template locally.
Implementation
definitionProvider
to the capabilities so this option will show on the menu and otherwise be availablehover
but with some modifications for the definition use casetemplate
items will work@self
will work