You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update: Add catchNoFixerButFixableProperty option (default false) to catch non-fixable rules that enable the fixable property in require-meta-fixable rule (#165)
* New: Add `catchNoFixerButFixableProperty` option (default false) to catch non-fixable rules that enable the fixable property in `require-meta-fixable` rule
* add tests
* fix variable name
meta: { fixable:'code' }, // property enabled but no fixer detected
52
+
create (context) {
53
+
context.report({ node, message:'foo' });
54
+
},
55
+
};
56
+
```
57
+
47
58
Examples of **correct** code for this rule:
48
59
49
60
```js
@@ -77,6 +88,12 @@ module.exports = {
77
88
};
78
89
```
79
90
91
+
## Options
92
+
93
+
This rule takes an optional object containing:
94
+
95
+
*`boolean` — `catchNoFixerButFixableProperty` — default `false` - Whether the rule should attempt to detect rules that do not have a fixer but enable the `meta.fixable` property. This option is off by default because it increases the chance of false positives since fixers can't always be detected when helper functions are used.
0 commit comments