fix(50750): Object type literal with string literal property in contextual typing position causes language service error on all literal type references

[Oleksandr Tarasiuk (a-tarasyuk)]

Fixes #50750

[Nathan Shively-Sanders (sandersn)]

I'd like to find and augment the skip-typed-jsdoc code in services instead of checking for undefined symbols in the checker.

[Daniel Rosenwasser (DanielRosenwasser)]

Hm - maybe. What about @link which really does need to semantically refer to the TS declaration?

[Nathan Shively-Sanders (sandersn)]

This should only apply to type-related jsdoc.

@link refers to values or types, but it's resolved in a services-only code path iirc. I don't think the binder visits it either. Actually, I don't know how (or whether) rename works on @link references in TS or JS.

Edit: Oh, it works because all the services calls to get a symbol go through getSymbolAtLocation, which has the @link/see name resolution code. I suppose that skipping type-related jsdoc references in getSymbolAtLocation might be an OK place if there isn't already code for it somewhere else.