NS2002 falsely triggered by optional ctor args about nsubstitute.analyzers HOT 5 OPEN

Actually, I'm unsure of this.

Forgetting about the analyser for now (I just disabled it), I nonetheless get this exception;

Exception thrown: 'Castle.DynamicProxy.InvalidProxyConstructorArgumentsException' in Castle.Core.dll

Weird, those args are optional, I'd have thought this would work?

from nsubstitute.analyzers.

Hi @lonix1. As you've seen Castle.Core throws exception even though parameters are options, that is why NSubstitute.Analyzers reports warning. Perhaps we should change warning message to sth more self explanatory. @dtchepak any thoughts on that?

Weird, those args are optional, I'd have thought this would work?

I assume this is limitation of Catle.Core rather than issue with NSubstitute itself, however I dont know that much about internals of NSubstitute. @dtchepak do you maybe know if this is this known problem of Castle.Core?

from nsubstitute.analyzers.

Your idea of a more descriptive warning is good. It will let the user know that it is "normal" and there is nothing he can do about it.

from nsubstitute.analyzers.

IIRC optional arguments are injected at compile-time? In that case Castle.Core will have no way of knowing what to pass to the constructor. (see also this thread).

Does Roslyn provide access to optional param information? If so maybe that should be a new error explaining optional parameters must be passed explicitly (possibly quick fix to pass the defaults?).

from nsubstitute.analyzers.

Does Roslyn provide access to optional param information? If so maybe that should be a new error explaining optional parameters must be passed explicitly (possibly quick fix to pass the defaults?).

Yes, we can extract default values with Roslyn

I will try to figure out how to use it in ctor matching logic

from nsubstitute.analyzers.