-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for source generators? #14
Comments
I would appreciate if you could provide a sample project ( |
here is a sample project. go to definition on the |
Edit: Likely related from upstream: dotnet/vscode-csharp#6426 I think this issue is keeping me from searching for workspace symbols using telescope in a project that uses source generators, meaning I would need to search for files instead. I think a band-aid fix for now would be for this to ignore invalid URIs if possible, that would at least allow searching for non-generated symbols. I'd be interested in fixing this, as otherwise this client is a lot better than omnisharp, but I have no idea how. Example from a godot project:
|
I've updated my version to 4.10.0-1.24058.1, which is the version currently tracked by the vs-code plugin. This fixes the issue with workspace symbols throwing an error in telescope for me, but the resulting file is empty. Attempting to navigate to implementations on a partial type with source generated implementations still throws the following error:
Edit: Annoyingly, this still fails if you use a |
I'd be curious if this will work for something like CommunityToolkit.MVVM too. I'd love to use this plugin for MAUI development |
in a project using a source generator I find that a go to definition results in
similar with a find references:
is there any way to support this?
tried updating to
opts.roslyn_version = "4.9.0-2.23563.2"
but that alone doesn't do itThe text was updated successfully, but these errors were encountered: