Feature to turn off emitting ModuleInitializerAttribute when bringing your own polyfills

[scooter12]

Added ability to recognize CompilerVisibleProperty set properties for controlling source generator options.
Added new build project property SgfAddModuleInitializerAttribute which when included in a source gen project's build pipeline and set to false (most commonly set in the project's .csproj file) will prevent the SgfAddModuleInitializerAttribute polyfill from being emitted. Use case is when utilizing other polyfill libraries.

[ByronMayne]

I am happy someone came in and fixed up all my typos, It's like I am at work haha. I will take a look at this tonight. Thanks for putting the effort into adding these features.

The other options instead of using an attribute was rapping the polyfils with per-processor definitions which you can just turn off.

#if SGF_DISALBE_POLYFILS
  // blah 
#endif 

The advantage being you have to do less inspections

[scooter12]

No problem! I've been messing around with SGF for about a year now on and off trying out different ideas. I really think SGF might be the most important sg project on github. We're in the process of using SGF to create a generic template driven sg. It's basically the bastard child of SGF, Moxy.Morris, and SourceGeneratorQuery. At least for us, 99% of a sg's usefulness is applying facets to POCOs and enforcing standardized patterns. As an example everyone can understand, marking a poco field as [ObservableProperty]<https://learn.microsoft.com/en-us/dotnet/communitytoolkit/mvvm/generators/observableproperty> or [DependencyProperty]<https://github.com/HavenDV/DependencyPropertyGenerator> in a WPF viewmodel, but where you yourself control the emitted code instead of relying on someone else's potentially malformed concept or outdated design. The real magic will be when I can implement an entire builder/factory pattern without all the boilerplate. Anyway, glad to help out where and when I can. I've got another commit I'm sitting on that's a complete "apply coding style" update but I don't want to submit it unless your ok with the idea since literally every file is changed. Have a great holiday weekend (assuming you're in the US) --Scott

[ByronMayne]

Would it be possible to break the MR into two different ones?

1. Added support for not adding ModuleInitializerAttribute polyfill
2. Fixed Grammatical Errors and Typos

Just so the release notes will be more clear. Besides for that I have no problems merging it in

[scooter12]

Yep. Done.

[ByronMayne]

Amazing thank you!