Skip to content
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

When an analyzer fails to load, log an error #1972

Merged

Conversation

jasonmalinowski
Copy link
Contributor

Right now we just silently fail which isn't a good debugging experience. Ideally these would be shown in the error list but this is good enough when trying to track things down.

Copy link
Member

@filipw filipw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks, makes sense. there is a somewhat related thing to it that for code actions that come from predefined assemblies (roslyn features. roslynator etc) we currently ignore those with generics (in case you'd wonder why something should light up but it doesn't)

// TODO: handle providers with generic params

Right now we just silently fail which isn't a good debugging experience.
Ideally these would be shown in the error list but this is good enough
when trying to track things down.
@JoeRobich JoeRobich merged commit 22387e5 into OmniSharp:master Oct 6, 2020
@jasonmalinowski jasonmalinowski deleted the log-analyzer-loading-errors branch September 16, 2021 23:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants