Skip to content

goToDefinition for pattern ambient module no longer goes to implementation #2426

@aaronadamsCA

Description

@aaronadamsCA

After switching to tsgo, command-clicking a .css import no longer opens the .css file. It just opens the pattern ambient module declaration.

Steps to reproduce

I'm pretty sure this test suite diff is already reproducing this issue:

--- old.goToDefinitionCSSPatternAmbientModule.baseline.jsonc
+++ new.goToDefinitionCSSPatternAmbientModule.baseline.jsonc
@@= skipped -0, +0 lines =@@
// === goToDefinition ===
-// === /index.css ===
-// [||]html { font-size: 16px; }
-
// === /types.ts ===
// <|declare module [|"*.css"|] {
// const styles: any;

Behavior with [email protected]

Go-to-Definition = Go-to-Implementation 👍

Behavior with tsgo

Go-to-Definition = Go-to-Type-Definition 👎

Metadata

Metadata

Assignees

No one assigned

    Labels

    Domain: EditorRelated to the LSP server, editor experiencebugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions