[英]Can I add my React.Component subclass to ESLint rules?
I am working on a project which builds an ES6 React App with Webpacker.我正在开发一个使用 Webpacker 构建 ES6 React 应用程序的项目。 We're using ESLint to keep our scripts tidy with some pre-commit hooks, but there is one issue I haven't been able to resolve.
我们正在使用 ESLint 通过一些预提交钩子来保持我们的脚本整洁,但是有一个我无法解决的问题。 We have a couple of
React.Component
sub-classes that we use and they aren't being detected as Components
by ESLint.我们有几个我们使用的
React.Component
子类,它们没有被 ESLint 检测为Components
。
Example Components:示例组件:
/* AsyncComponent.jsx */
export default class AsyncComponent extends React.Component {
// Sub-classes will define _render() instead of render()
render() {
if (this.isLoaded()) {
this._render();
}
}
// "Virtual" functions which must be defined by sub-class
// isLoaded() {}
// load() {}
// _render() {}
}
/* MyComponent.jsx */
export default class MyComponent extends AsyncComponent {
// This works, but is not parsed as a Component by ESLint
// Define our "virtual" AsyncComponent functions
isLoaded() {}
load() {}
_render() {}
}
MY QUESTION: I would like to know if it is possible to configure ESLint to detect AsyncComponent
sub-classes such as MyComponent
as React.Component
sub-classes and apply the same rules that it would to other Components
.我的问题:我想知道是否可以配置 ESLint 来检测
AsyncComponent
子类,例如MyComponent
作为React.Component
子类,并将相同的规则应用于其他Components
。
BONUS QUESTION: This may cause an issue with the _render()
method that this particular example uses, so it would also be helpful if I could override the eslint-react rules to expect _render()
instead of render()
within AsyncComponent
sub-classes.额外问题:这可能会导致此特定示例使用的
_render()
方法出现问题,因此,如果我可以覆盖 eslint-react 规则以期望在AsyncComponent
子类中使用_render()
而不是render()
也会有所帮助.
Relevant dependencies from package.json
:来自
package.json
相关依赖项:
"eslint": "^5.11.1",
"eslint-config-airbnb": "^17.1.0",
"eslint-plugin-import": "^2.14.0",
"eslint-plugin-jsx-a11y": "^6.1.2",
"eslint-plugin-react": "^7.12.2",
"eslint-plugin-promise": "^4.0.1",
"eslint-plugin-react-redux": "^3.0.1",
"react": "^16.7.0",
"react-dom": "^16.7.0",
"react-redux": "^6.0.0",
"redux": "^4.0.1",
Relevant config from .eslintrc
: .eslintrc
相关配置:
"extends": [
"airbnb",
"plugin:react-redux/recommended",
"plugin:promise/recommended"
],
"parser": "babel-eslint",
"parserOptions": {
"ecmaVersion": 8,
"ecmaFeatures": {
"experimentalObjectRestSpread": true,
"impliedStrict": true,
"classes": true
}
},
"env": {
"browser": true,
"node": true,
"jquery": true,
"jest": true
},
"plugins": [
"react-redux",
"promise"
],
I'm not sure what you are trying to achieve.我不确定你想要达到什么目标。 I think you could try return super.render()
我想你可以尝试 return super.render()
render() {
if (this.isLoaded()) {
super.render()
}
}
But its a bad idea to extend components like this as the above says use hooks, Hocs or renderProps patterns for this kind of stuff, I know it can be confusing , especially if you come from an 'OO' background, but taking the approach you have done will be more trouble than its worth.但是像上面所说的那样扩展这样的组件是一个坏主意,对这类东西使用钩子、Hocs 或 renderProps 模式,我知道这可能会令人困惑,尤其是如果您来自“OO”背景,但采用这种方法已经做了会比它的价值更多的麻烦。
Thanks to @fard for his suggestion.感谢@fard 的建议。 I was trying to do this the wrong way... seems like React Higher-Order Components are the right way to do what I'm trying to achieve here.
我试图以错误的方式做到这一点......似乎React 高阶组件是完成我在这里尝试实现的目标的正确方法。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.