thenameless314159 / sourcegeneratorutils Goto Github PK

The goal of this would be to force the usage of global:: directives and disable the possibility to add using directives as these are bad practices for generated source files. Not sure yet about how to enforce the usage of global:: directives though

Could allow users to define using within the namespace declaration (afterward), this would require to make a different logic for #2 since the all contained namespaces would have to be trimmed

The target type containing types are currently written simply like this writer.WriteLine($"{type.Accessibility ?? publicKeyword} {type.Type} {type.Name}");, the goal was to allow source generator users to handle containing partial types (when logic needs to be generated for a nested class) but the scope of this library is also general-purpose code generation therefore they should be handled like target types

Resources could be excluded via their fully qualified type name, the reason this wasn't implemented in the 0.0.1 is because some types are generic and it'd require to either :

• rename every file with their fully qualified type name (and therefore make sure that in the future every new type introduced follows this logic)
• or parse the type declaration from the source code, which would be more convenient but won't be possible until #43 have been resolved

This will give an example on how to implement the provided abstractions and give a starting point for most general purpose source generators.

Using directives declaration in CSharpSourceFileGenerator<T> should add a filter if a namespace is contained within the target namespace.

xml documentation may contain colons which are checked for base type inheritance, a quick fix would be to check the last line only of the type declaration

Would require #44 to be resolved

This should fix #3

As described in this issue on the roslyn repository: dotnet/roslyn#47517.

Could remove the need for strongly-typed source file/block generator

• With the possibility to add attributes to the type declaration (generated code, exclude from coverage)
• And to extract the fully qualified type name

Currently they're ordered by descending, should make this configurable

• TypeSourceFileEmitter should become SourceFileEmitter
• GetSourceCodeWriters() could take the target spec as an arg
  • May become a virtual member that returns an empty enumerable by default

For top-level namespace