Anonymous functions cause 'Unable to Open' error in VSCode

[jonathan-spruce]

In VSCode, when clicking on the details section of a problem where the parent caller was an anonymous function, it shows an error:

We probably just need to disable trying to link at all when the parent caller is an anonymous function.

[tetchel]

They still appear under the correct file, so why shouldn't they have the same URI as the other markers on that file?

[jonathan-spruce]

You're right, and it also shows the line number it thinks it is. I'll do some more investigation because it looks like this should be working.

[tetchel]

The (1, 1) is default, it'll show even if you pass undefined or a line that doesn't exist.

Unrelated but I think it's dumb that a position is always shown because not all warnings map to a position (such as my "missing files" errors in the Microclimate extension)