Finding your way
Go to definition and references
Finding your way · 1 min read
Click a name to see where it was made, or to see everywhere else it is used. A small preview opens under the line so you do not lose your place.
When you would want it
It is the difference between reading code and searching it. Following a function to its body is the single most common thing anybody does in an unfamiliar project.
Where to find it
- All Features → Go to definition and references
- Go to definition
- Peek definition
- Turn on or off
- Settings
What you get out of it
- Following a call to its source takes one click, not a search-and-scroll.
- The resolved/matched label tells you when to trust the answer fully.
How to use it, step by step
- Click a name - a preview of its definition opens under the line, keeping your place.
- Click the preview's title, or Ctrl+click the name, to actually jump there.
- Press Escape to close the preview when it answered the question.
- Read the honesty label: 'resolved' means a language server found it for certain; 'matched by name' means same-name candidates.
Why this beats the usual way
Most editors either have a server and get this right, or silently guest-match by name and get it plausibly wrong. Showing which kind of answer you got removes false confidence from the fallback.
Find it in Universal Search
Go to definition and references · Finding your way