puppetlabs / puppetlabs/puppet-editor-services
Feature: Go to Implementation for control-repo
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 52
- Forks
- 21
- Avg merge
- 15h
- Merged PRs (30d)
- 3
Description
For control-repo's, we have the ability to right-click and press "Go to Definition" on a type/provider, which brings us into the type file.
It would be nice to have a similar approach, leveraging the Go to Implementation API, to bring us into the provider file.
I often find myself pressing "Go to Definition", just to bring me the the type, so its easier to find the provider. This would save a couple of clicks :)
As a user/developer
I would like to go to my custom providers easier
so that I don't have to click and scroll after it
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the language-server code that currently supports Go to Definition and review VS Code's Go to Implementation API. Trace how control-repo type/provider links are resolved, then verify navigation from a custom type to its provider in VS Code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby, vscode
- Domain
- developer-experience, devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100