Open ushenkodmitry opened 5 years ago
So, this works with the new message initializers in MassTransit, and it's likely that the capability in GreenPipes will be removed in favor of the new initializer style.
Do you want to drop TypeCache<> from GreenPipes entirely? Or just leave it as it is?
I haven't really thought about it, but I doubt it. I'll likely just get rid of the mapping logic and replace it with the initializer code.
Just want to say that GreenPipes is awesome lib, i'm using it on several projects. Some my code tight to TypeCache API (don't know if it was good idea to tight to API from the internals namespace, but...). So i'm voting for leaving TypeCache API in GreenPipes in some form.
Good to know, and yes, it will stay in GreenPipes. I've thought about moving it out to a separate library, but then it's just one more assembly to manage...
Hey, attempt to initialize proxy object of the class, that has a property of same type as class itself causes a StackOverflowException to be thrown. For example initialization of proxy class for ExceptionInfo interface (from MassTransit) throws: