You should do it like this: Or if you want to go one lever deeper: But in that case the navigation object should be defined. Although it is possible to give a default value for destructuring objects. E.g. Now navigation will be an empty object if it’s undefined.
Either change your file extensions to .jsx as mentioned or disable the jsx-filename-extension rule. You can add the following to your config to allow .js extensions for JSX.
you should bind the function to this as the ESLint error says “Expected ‘this’ to be used by class method ‘getUrlParams’ as you are not using getUrlParams during render (like onClick()) so the above technique is good which we can call it “usage of arrow function in class property”. there are other ways of binding … Read more
https://github.com/evcohen/eslint-plugin-jsx-a11y/blob/master/docs/rules/click-events-have-key-events.md It seems this rule is to enforce Accessibility standards. Based on this, change your code to do something like this You could also disable the rule in eslint, I suppose it depends on preference.
https://github.com/evcohen/eslint-plugin-jsx-a11y/blob/master/docs/rules/click-events-have-key-events.md It seems this rule is to enforce Accessibility standards. Based on this, change your code to do something like this You could also disable the rule in eslint, I suppose it depends on preference.
Create a .eslintrc.js in the directory of your file, and put the following contents in it:
Check if you have the linebreak-style rule configure as below either in your .eslintrc or in source code: Since you’re working on Windows, you may want to use this rule instead: Refer to the documentation of linebreak-style: When developing with a lot of people all having different editors, VCS applications and operating systems it may occur that different line endings … Read more
Unexpected token errors in ESLint parsing occur due to incompatibility between your development environment and ESLint’s current parsing capabilities with the ongoing changes with JavaScripts ES6~7. Adding the “parserOptions” property to your .eslintrc is no longer enough for particular situations, such as using in ES6 classes as ESLint is currently unable to parse it on … Read more
You need to define propTypes as a static getter if you want it inside the class declaration: If you want to define it as an object, you need to define it outside the class, like this: Also it’s better if you import prop types from prop-types, not react, otherwise you’ll see warnings in console (as preparation for React 16):
Exporting an arrow function directly doesn’t give the component a displayName, but if you export a regular function the function name will be used as displayName. You can also put the function in a variable, set the displayName on the function manually, and then export it.