Ctrl Click/ F12 on a function doesn't take you to definition (vs code)

[goleary]

When I Ctrl+ click a function or component in VS Code (or use F12) I'm taken to the import statement at the top of the file I'm already in, not the definition in that file. I figured maybe this had to do with the src/... aliasing, but even when I import regularly this is still happening.

https://code.visualstudio.com/docs/editor/editingevolved#_go-to-definition

This makes it difficult to get to the definition of a function/component.

vs code 1.45.1
windows 10

[peterp]

I'll take a look at this, thanks for reporting it!

[jtoar]

Here's an example I came across:

go-to-def.mp4

[Tobbe]

This is one of the things I miss the most when working on a RW project compared to say a CRA project. Thankfully it's going to be solved by our TS efforts. It's the second to last item here #234 (comment)

[dac09]

Fixed in #2614 !! 🍾