Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Enabling C# 8 nullable reference types throws exception on interface messages #5488
Message contracts defined using interfaces will cause endpoints to throw
All users defining messages using interfaces with nullable reference types turn on.
Our custom message mapper was not prepared for the attributes emitted by the compiler.
I had a faint memory that you could exclude certain files/types from being included but I can't find anything in https://docs.microsoft.com/en-us/dotnet/csharp/tutorials/nullable-reference-types
So there is no workaround that can get you unstuck other than turning the nullable ref types off for the csproj that contains the message contracts?
Yea we should fix this. Just wanted to get a feel of the urgency?…
On Wed, 13 Nov 2019 at 11:22, Simon Cropp ***@***.***> wrote: why not fix the underlying issue, that the proxy generation makes assumptions about the nullability of parameter names? is my others pr a viable start to that? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#5488?email_source=notifications&email_token=AAA6QZG5OSP4GUHOVLI5AXLQTPINJA5CNFSM4JL7MX22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOED5UHRA#issuecomment-553337796>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAA6QZE4RRJHUCCHUPKYAITQTPINJANCNFSM4JL7MX2Q> .