-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generate GenerateAutomaticInterfaceAttribute #47
Generate GenerateAutomaticInterfaceAttribute #47
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also please increment the major version - this is a breaking change
….com/crwsolutions/net_automatic_interface into feature/generate-interface-attribute
Just to dust off this PR :): Hi, I've added a step in the README, to add the using statement. So if you are happy with it this can be merged now in my opinion. But it is also possible to remove the namespace for some extra convenience (would be mine preference). I would also like to highlight in that case, that the generated Attribute is internal. So the probability of conflicts is really about zero. |
Any chance that this gets merged and released in a foreseeable time frame @ChristianSauer? I would really like to start working on some new features (like custom interface name and get only properties in interfaces), but I consider this a prerequisite. |
@ccHanibal @crwsolutions I've finally merged it. Sorry, where a shitty few months |
Generate GenerateAutomaticInterfaceAttribute instead of asking that of the user.
See cookbook:
https://github.com/dotnet/roslyn/blob/main/docs/features/incremental-generators.cookbook.md#generated-class
If you're feeling adventurous, it is possible to remove the namespace from the generated attribute (so remove 'namespace AutomaticInterface'). That would give even more convenience. Given the name of the attribute I think there is very little change of type conflicts.