Make consistent-destructuring configurable
unicorn/consistent-destructuring seems to trigger in multiple scenarios. We would ideally be able to control which specific cases are active.
For example this seems to always be good
function example(o) {
const { a } = o;
console.log(a);
// Please do complain that I've already got a const for a 👍
console.log(o.a);
}This scenario in particular I don't like, and would want to turn off:
class Example {
example() {
const { a } = this; // rule wants me to write const { a, expensive } = this
if (a) {
// this.expensive is not being consistently destructured
// but i don't want to call the expensive getter unnecessarily in the const above
console.log(this.expensive);
}
}
get expensive() {
// Something that requires significant compute
}
}
sindresorhus / eslint-plugin-unicorn
More than 100 powerful ESLint rules
4.2k
How does funding with Polar work?
1
Pay now to fund the work behind this issue.
2
Get updates on progress being made.
3
Maintainer is rewarded once the issue is completed.
FAQ
Backer
You're funding impactful open source efforts
Contributor
You want to contribute to this effort
Maintainer
You want to get funding like this too