fisker Cheung
fisker Cheung
> I'm surprised that there's no rule or rule suggestion for for-in though. There seems no rule forbids `for..in` loop, but only [`guard-for-in`](https://eslint.org/docs/latest/rules/guard-for-in). Fun fact: This is valid 😄 ```js...
Sorry, we can't know the type of `authLink`
Adding `object: 'Array'` means the selector only matches `Array.concat()` it's for static methods.
We may consider and option to ignore `.concat()`, but absolutely not suggesting the opposite.
FYI: I just finished refactoring Prettier codebase [from `.concat()` to `...` ](https://github.com/prettier/prettier/pull/10129), it's much more clear that the argument is an array or not, and during that refactor, I realized...
> I'm wondering if this conditional/check should be changed to: No, we can't, most time `staticResult` can't be calculated, even this simple code ```js class A {}; const foo =...
Transferred from prettier repo.
I think it's caused by the next call after https://github.com/prettier/prettier-cli/blob/4b1a66a1b8d7091ba53a37b4762b7863eaf09585/src/utils.ts#L248 been executed, it will override `targetFilesNamesToPaths.propertyIsEnumerable` to an array.
Change to `Object.property.propertyIsEnumerable.call()` should fix it.
Any progress here?