Raoul Wols
Raoul Wols
While we use v1.38.2: https://github.com/sublimelsp/LSP-OmniSharp/blob/1afed47ed5aebc692c6c69220c80ce79b9cebc0f/plugin.py#L15
Is your folder called “$metadata$“ ?
Can you open the LSP Log Panel (from the command palette) and post the exact request to the OmniSharp server and corresponding response here?
Just to be clear, you’re trying to goto-def on something internal to Unity? If so, it seems that $metadata$ is supposed to be a marker to possibly disassemble a Unity...
We can look at what the VSCode extension is doing in such cases and translate it to Python
You seem to be right on the mark with that link. Crucially, I think we need to request "metadata info" with a custom request to resolve things: https://github.com/OmniSharp/omnisharp-vscode/blob/77ec34e0080939a02e15a63a06e005f2098134b6/src/omnisharp/utils.ts#L136 Kind of...
I’m open to support this when you create a pull request for this functionality.
cshtml seems to be handled by "Razor". It's an additional plugin that needs to be downloaded: https://github.com/OmniSharp/omnisharp-vscode/blob/6608b739146123e920f410da5f29b9abfa8309eb/src/omnisharp/server.ts#L322-L326
more info here https://github.com/OmniSharp/omnisharp-vim/issues/546
v1.39.0 removed the bundled mono, so we'll have to take care of this anyway: https://github.com/OmniSharp/omnisharp-roslyn/releases/tag/v1.39.0 See: https://github.com/OmniSharp/omnisharp-roslyn/issues/2339