csharp-source-generators VS NullGuard

I don't know of anything out of the box that would emit errors/warnings for a case like that, but if it was something you were dealing with often enough you could certainly write your own analyzer if one doesn't already exist.

List of source generators: https://github.com/amis92/csharp-source-generators

I also couldn't find many info in docs nor more advanced tutorials, but this list of source generators helped me as an inspiration.

I'm planning to rewrite all of our company's old T4-based codegen tools into Source Generators. I've been looking at how other Source Generators are implemented and what surprised me is that everyone seems to assemble the output code manually as text with string builders or at best some simple templating engine (eg. Scriban). I expected that I would see a lot of projects assembling their output code from Roslyn tokens and then using Roslyn's formatter to produce the actual code that can be emitted into the output file(s), like this article demonstrates. No-one seem to be doing that though. Why?

Start from here: C# Source Generators

Look here under 'Tips & Tricks'

Source generators colletion

Add it to this list https://github.com/amis92/csharp-source-generators

Nullable reference types + https://github.com/Fody/NullGuard

I find Nullable Reference Types combined with NullGuard to be pretty good.

For example here from the readme I can exactly see what boilerplate is generated for me.

Some tools can help to enforce this convention like ReSharper and NullGuard. I guess, although I haven’t tried this yet, you can add a custom rule to SonarQube which will alert when the word null appears.