fisker Cheung
fisker Cheung
@SamChou19815 Sorry for bothering, can you take a look?
We support vue SFC years ago, [this](https://github.com/sindresorhus/eslint-plugin-unicorn/pull/1360) is the first one. > but we need to consider what the API should be. If it's possible, `scopeManager` should work directly. `eslint-plugin-vue`...
Can you try ```diff module.exports = { arrowParens: "avoid", endOfLine: "lf", printWidth: 80, tabWidth: 2, trailingComma: "es5", overrides: [ { - files: "*.css", + files: "**/*.css", options: { parser: "css",...
@43081j I thought this was fixed? Related PR https://github.com/prettier/prettier-cli/pull/34
Maybe we should just disable auto-fix on this rule https://github.com/sindresorhus/eslint-plugin-unicorn/issues/418#issuecomment-542207903
I Don't think this is bug, and the auto-fix will be removed in #666
We can't know `source` is not `Array` and `uid` is not a function. So... I guess you'll have to use `eslint-disable` or ```js const response = await source.find("some uid"); //...
I tried really hard to rewrite this rule , and you can see it did catch a lot of problems in https://github.com/sindresorhus/eslint-plugin-unicorn/pull/666 . Big problem is we can't know if...
It's not `auto-fixable` now , means if we set to `warn` , your code won't be changed even with `--fix`, should we do that ?
That is exactly why this rule exists, it is problem.