Go To Source Definition UX improvements #152252
Labels
feature-request
Request for new features or functionality
javascript
JavaScript support issues
typescript
Typescript support issues
ux
User experience issues
Milestone
Following up on TypeScript’s new Go To Source Definition command (d851ea5), I want to track some editor-side UX improvements:
Can we replace the error notification for “no source definitions found” with an inline message similar to Go To Definition?
Can we somehow indicate when a result is a guess? This is already returned in the protocol response via an
unverified
property, but it is never surfaced to the user. When multiple locations are returned, maybe we could add something to the peek locations UI:(Note: the
unverified
flag is also sometimes set in normal Go To Definition responses, so this request is not specific to Go To Source Definition.)When only one location is returned, maybe a notification would suffice, but I would love design input on this.
The text was updated successfully, but these errors were encountered: