Feature Request: Attribute Filtering about autointerface HOT 2 CLOSED

It is unlikely that the generated attributes of AutoInterface influence the generation of Mapperly, because source generators are independent from each other. Each source generator gets as input the source code before any generation. A source generator cannot see the output of another generator, so for Mapperly the generated interfaces does not exist.

Maybe the problem is exactly that: Somewhere Mapperly needs to read an interface, but the interface is not present because it will be generated by AutoInterface and Mapperly is not able to see it. And when the interface is created manually, Mapperly has no problems finding the interface.

Another thing that is possible is when working with multiple .csproj/assemblies. When code is generated in the first .csproj and the second .csproj has a reference on the first .csproj, then the generated code of the first .csproj is visible for the generators of the second .csproj.
In this case the generated attributes of AutoInterface are visible to Mapperly, but the [Mapper]-attribute is not present at the interface, so it should not affect anything.

I want to wait until you pin-point the exact cause before making a decision, because I still think that the attributes do not harm and the cases they do harm are so rare, that this feature is not worth it.

In case you do not know, you can use <EmitCompilerGeneratedFiles>true</EmitCompilerGeneratedFiles> to save the generated source code to disk.
Good Luck

from autointerface.

The team was able to reproduce the bug without AutoInterface involved at all. So their initial assumptions were incorrect and therefore this feature request should not be needed. Thanks for the consideration.

from autointerface.