Axetroy
Axetroy
@sindresorhus Is this rule acceptable?
Should we allow `this` in the top-level scope? Many umd modules and some special environments may not have `window` and `global,` and this is needed for detection ```js (function (root,...
> Also, should we allow `this` in object methods? It should be allowed, Vue2 options is this mode, otherwise there are many false positives ```vue export default { methods: {...
Examples of false positives ```js new SDK({ appKey: 'xxx', appId: 'xxx', onReady: function () { this.xxxxx } }) ``` ```vue export default { methods: { refresh: debounce(async function () {...
Vue2 is EOL, But Vue's options mode is not. And similar situations ```js export default defineComponent({ methods: { mounted() { this.xxxxxx // } } }) ``` Maybe we should wait...
> Overlap with: > > * [Only functions names can have verbs (get, set, create, remove) #617](https://github.com/sindresorhus/eslint-plugin-unicorn/issues/617) > > * [Rule proposal: Ensure special verbs match the type (e.g. `hasName`...
@fregante I plan to implement this. But I'm not sure if I should merge these into one rule. Because these look similar, But writing it into one rule will increase...
Before I start, I need to make sure that whether the property also needs to be checked, as it cannot be safely fixed. In my current implementation, I have intentionally...
`typeof window` is a shorthand way of writing `typeof globalThis.window` So it should not emit an error. This seems reasonable. same as `self`