Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
"destructured" option for camelCase rule #3185
Thanks for the issue! We get a lot of issues, so this message is automatically posted to each one to help you check that you've included all of the information we need to help you.
Reporting a bug? Please be sure to include:
Requesting a new rule? Please be sure to include:
Requesting a feature? Please be sure to include:
Including this information in your issue helps us to triage it and get you a response as quickly as possible.
Since the pattern key is "external" code*, my first reaction is that we should be ignoring that by default, no option necessary. Thoughts?
*If it comes from a response, then it's truly external. If it comes from an object created elsewhere, camelcase will catch the issue then. Either way, the local variable is what matters.
Sorry, I meant to say "request" not "response".
I can do it without destructuring:
here's a more simple use-case: