Jeroen Vannevel

Similar to what others mentioned, I had this issue with subscriptions. Doesn't work: `import { useSubscription } from '@apollo/client/react/hooks/useSubscription';` Works: `import { useSubscription } from '@apollo/client';`

I went with https://github.com/agnat/node_mdns and that worked from the get-go

Hi @michalss. I make a change to this repo from time to time when people ask me about it. I created it once for my own benefit 7 years ago...

Have a look at https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/d10db47a8777dc882ef196d78692a1ece67bbb1d/StyleCop.Analyzers/StyleCop.Analyzers/GeneratedCodeAnalysisExtensions.cs#L109 for an example exclusion implementation

This should include `Migration` classes for EF

Related to Vannevelj/SharpSource#72

Did VSD explicitly account for this in the code? Regardless: I think `_camelCase` is probably best.

The syntax for this feature is ``` public int MyProperty { get; set; } = 10; public IList MyProperty { get; } = new List(); ``` which provides a default...

A fix should only be added if it's an auto-property -- no point in trying to figure out something that can have so many different edge cases

Are the bugs related to it being a vsix or just general VSDiagnostics bugs?