eslint

问题 I have put my react-navigation code into a separate Routes file which I am then importing into my App.js file. Everything is working fine but I am using Airbnb ESLint config in Atom/Nuclide and getting an error with tintColor... "tintColor is missing in props validation" Tried this: Routes.propTypes = { tintColor: PropTypes.string.isRequired,} But then get error "tintColor PropType is defined but prop is never used" This is part of the code const Routes = () = { const ContentNavigator =

问题 I am using EJS as my view engine on a node and express setup. I want to use ejs-lint to help get the line for errors. I haven't use a linter before, but from reading through the documentation here: https://github.com/RyanZim/EJS-Lint I'm assuming you can just check errors on a specified file in command line like this: ejslint Are my assumptions right and what am I doing wrong? I've already installed using npm install ejs-lint --save-dev Also, if I plan to add ESlint to my project I'm guessing

问题 my team is working on project using Angular 1.5.* + typescript. Can someone give me advice for best TSLint configuration for such project as mine? I want now to add TSLint config ( https://github.com/Microsoft/TypeScript/blob/master/tslint.json) from official TS repo and with ESlint rules set. https://github.com/Microsoft/TypeScript/blob/master/tslint.json Will it be enough? What do you think? Thank you in advance for your answers. 回答1: Will it be enough? What do you think? Personally I don't

问题 How do I add a display name to this? export default () => <Switch> <Route path="/login" exact component={LoginApp}/> <Route path="/faq" exact component={FAQ}/> <Route component={NotFound} /> </Switch>; 回答1: Put the function in a variable, set displayName on the function, and then export it. const MyComponent = () => ( <Switch> <Route path="/login" exact component={LoginApp}/> <Route path="/faq" exact component={FAQ}/> <Route component={NotFound} /> </Switch> ); MyComponent.displayName =

问题 How do I add a display name to this? export default () => <Switch> <Route path="/login" exact component={LoginApp}/> <Route path="/faq" exact component={FAQ}/> <Route component={NotFound} /> </Switch>; 回答1: Put the function in a variable, set displayName on the function, and then export it. const MyComponent = () => ( <Switch> <Route path="/login" exact component={LoginApp}/> <Route path="/faq" exact component={FAQ}/> <Route component={NotFound} /> </Switch> ); MyComponent.displayName =

问题 How do I add a display name to this? export default () => <Switch> <Route path="/login" exact component={LoginApp}/> <Route path="/faq" exact component={FAQ}/> <Route component={NotFound} /> </Switch>; 回答1: Put the function in a variable, set displayName on the function, and then export it. const MyComponent = () => ( <Switch> <Route path="/login" exact component={LoginApp}/> <Route path="/faq" exact component={FAQ}/> <Route component={NotFound} /> </Switch> ); MyComponent.displayName =

问题 I'm trying to set up ESLint in such a way that it parses a globals declaration file before linting the actual target file, so that I don't have to declare as globals all the functions and variables that are indeed globals, but letting the parser figure that out: In some_module.js : function do_something() { if (glob_action("foobar")) { ... something something ... } } While in globals.js I have a set of utilities and global variables: function glob_action(x) { ... something something ... } So

问题 I'm trying to set up ESLint in such a way that it parses a globals declaration file before linting the actual target file, so that I don't have to declare as globals all the functions and variables that are indeed globals, but letting the parser figure that out: In some_module.js : function do_something() { if (glob_action("foobar")) { ... something something ... } } While in globals.js I have a set of utilities and global variables: function glob_action(x) { ... something something ... } So

问题 I'm trying to set up ESLint in such a way that it parses a globals declaration file before linting the actual target file, so that I don't have to declare as globals all the functions and variables that are indeed globals, but letting the parser figure that out: In some_module.js : function do_something() { if (glob_action("foobar")) { ... something something ... } } While in globals.js I have a set of utilities and global variables: function glob_action(x) { ... something something ... } So

问题 I'm trying to set up ESLint in such a way that it parses a globals declaration file before linting the actual target file, so that I don't have to declare as globals all the functions and variables that are indeed globals, but letting the parser figure that out: In some_module.js : function do_something() { if (glob_action("foobar")) { ... something something ... } } While in globals.js I have a set of utilities and global variables: function glob_action(x) { ... something something ... } So