-
Notifications
You must be signed in to change notification settings - Fork 507
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SA1316 should not be reported for tuple deconstruction #3878
Comments
I am not seeing this behavior. Which version are you using? |
Have you set includeInferredTupleElementNames to true in your stylecop.json configuration file? I see the behavior that you describe when I do that. |
I have. It seems I'm misunderstanding what |
|
It looks to me like you have found a bug. In my opinion, tuple expressions used in the "target" of a deconstruction should not be checked by this rule. @sharwell, do you agree? I am a bit surprised that this hasn't been found before, but |
I see, thanks for the clarification |
It looks like setting |
Tuples can follow two different casing conventions depending on how it's used: tuple types may follow pascal casing, while deconstruction may follow camel casing
The rule does not differentiate between the two uses and indiscriminately flags both, so I propose having a separate rule for tuple deconstruction
The text was updated successfully, but these errors were encountered: