No semantic token assigned to import names, but available for export

🔍 Search Terms

• import (in the FAQ)
• is:issue is:open No semantic token import
• is:issue is:open No highlight import

✅ Viability Checklist

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

⭐ Suggestion

This is an issue originally from: https://github.com/typescript-language-server/typescript-language-server/issues/842 and https://github.com/microsoft/vscode/issues/202224.
The issue is confirmed not to be an issue from TypeScript Language Server by its' developer/maintainer, and it is suggested to be posted here by VSCode'sdeveloper/maintainer.

This feature request is asking for the implementation of the semantic highlighting for member imported in the import statement.

📃 Motivating Example

When export a name, there is semantic token assigned. Such as the Compiler is assigned with class.

For import, there seems to be no semantic token available.

And it is also predictable that import using this way, will also get no correct semantic token assigned.

💻 Use Cases

1. What do you want to use this for?

Bring better coding experience.

2. What shortcomings exist with current approaches?

Currently no precise token is assigned to the imported members, no semantic token is assigned.

3. What workarounds are you using in the meantime?

As a theme designer, I do not have any other ideas on that, and I believe this could be solved by language's implementation of this feature.

Start by reproducing the import and export examples in an editor with TypeScript semantic highlighting enabled, then trace how semantic tokens are produced for imported members. The issue names no source files or tests, so identify the relevant language-service token-generation entry point and add coverage showing the expected token assignment.