We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should be "extends": "@portto/eslint-config-portto/browser". Also need following package installed. Is it necessary?
"extends": "@portto/eslint-config-portto/browser"
yarn add --dev eslint-plugin-compat eslint-plugin-flowtype
semi: ['error', 'always']
'no-nested-ternary': 'error'
For example:
{status === ItemStatus.BUYING ? ( <Spinner /> ) : locked ? 'OUT OF STOCK' : 'BUY' }
'react/react-in-jsx-scope': 'error'
'react/jsx-filename-extension': ['error', { extensions: ['.js'] }],
import/extensions
Overall, TypeScript and ES6 is not support well. Maybe define a new eslint rule well be better?
The text was updated successfully, but these errors were encountered:
yanglin5689446
No branches or pull requests
Readme
Should be
"extends": "@portto/eslint-config-portto/browser"
.Also need following package installed. Is it necessary?
rules/base.js
semi: ['error', 'always']
Do we need semi every line?
'no-nested-ternary': 'error'
With prettier, nesting ternary expressions is acceptable now. And it will be more complicated in jsx if prohibited.
For example:
rules/react.js
'react/react-in-jsx-scope': 'error'
After React v17 this is no longer needed.
'react/jsx-filename-extension': ['error', { extensions: ['.js'] }],
We alse use TypeScripts now.
rules/import.js
import/extensions
missing .ts and .tsxOther
Overall, TypeScript and ES6 is not support well. Maybe define a new eslint rule well be better?
The text was updated successfully, but these errors were encountered: