`satisfies` is shown on go-to-implementation

[ulugbekna]

🔍 Search Terms

"satisfies", "go-to-implementation", "go to implementation", "implementation"

✅ Viability Checklist

• [x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
• [x] This wouldn't change the runtime behavior of existing JavaScript code
• [x] This could be implemented without emitting different JS based on the types of the expressions
• [x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
• [x] This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
• [x] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

⭐ Suggestion

Currently, "go to implementation" on a type functionality for typescript code in VSCode will go to places where an object of this type is created. This works

interface Person {
    name: string;
}

function f() {
    const john: Person = { name: 'John' }; // both this type annotation and `as` syntaxes show these objects as implementations of `Person` 

    const andrew = { name: 'Andrew' } as Person;

        const tyler = { name: 'Tyler' } satisfies Person; // this is not shown as an implementation of `Person` 
}

📃 Motivating Example

Go to implementation is a very easy way to see who produces objects of a particular type.

satisfies marking a type to adhere to a particular type without creating a new variable using type annotation syntax.

💻 Use Cases

1. What do you want to use this for? Identify implementations of a type.

2. What shortcomings exist with current approaches? None I can think of.

3. What workarounds are you using in the meantime? Going to references and reading code.