beakona

I've made [1.0.36-pre](https://www.nuget.org/packages/BeaKona.AutoInterfaceGenerator/1.0.36-pre) prerelease that should work as expected.

I've made changes. Only specific attributes are bing forwarded now. Here is the list: 1. `System.ObsoleteAttribute` 2. most of attributes from `System.Diagnostics.CodeAnalysis` namespace

Yes, you are right. It is easier to skip `return` target for properties and indexers and fall back to expanded version of that property.. If we have following: ```cs interface...

As I understood, you have following problems: - nullability - missing classes in netstandard2?? Nullability can be avoided by switching to newer language version. Add LangVersion in .csproj and reload...

I've made following changes: 1. have moved `Test` to `console application` 2. have changed access modifier of `NotNullWhenAttribute` from `internal` to `public` 3. added alias for `class library` inside `console...

I've made some final changes prior to release..

I thought about that feature and decided that it would add too much confusion because AutoInterface is primarily an interface helper tool and SimplePrinter does not implement IPrintableComplex. Match by...

I've made changes... Now, attributes attached to `value` parameter of each set method (for properties/indexers) [and add/remove methods for events] are being propagated to output.. I've discovered that `value` parameter...

Variable `references` is collection because there could be many fields/properties/indexers that should be called/accessed during forward-call. In example [multiple backers](https://github.com/beakona/AutoInterface/wiki/Examples#single-interface---multiple-backers) there are two fields paired to `IPrintable` interface. Expression `references.First().ReceiverType.IsMemberImplemented(i)`...

I've made nuget prerelease package [1.0.30-pre](https://www.nuget.org/packages/BeaKona.AutoInterfaceGenerator/1.0.30-pre) that should fix this issue.