Closed 0liver closed 6 months ago
Thanks for the contrib! Don't worry about the missing parent PR failing check, I'll add one.
Any particular reason why you didn't choose to keep the StyleCop rule instead?
Thanks! I had already forgotten that a parent PR is needed 😉
As for the choice of rule to keep - I think I liked the warning message better from S113
, but looking at the great rules provided by StyleCop, keeping SA1518
instead seems like a good idea, too. Would you like me to switch them around?
No, it's OK then. The StyleCop rule also requires some configuration so that makes things easier. Interestingly enough, we didn't actually add any config but it was still working, perhaps by some coincidence.
Thank you!
It's been a pleasure! 😊
There's another duplicate, CA1711
and S2344
:
Which one would you remove?
I'd need to dig into that, but the SDK one is usually a safer bet.
the SDK one is usually a safer bet.
To keep, I suppose?
I just discovered why picking S113 over SA1518 might have been the wrong choice - there's no quick-fix action available for the former, but there is for the latter, which is greatly appreciated when you want to clean up your solution one warning at a time 😉
Do you fancy another PR to invert the exclusion?
Yes, and sure, thanks.
Here's the follow-up PR: https://github.com/Lombiq/.NET-Analyzers/pull/97.