Set `tabWidth: 2` in Prettier config (#2438)
* chore: Update Prettier config, setting tabWidth:2
* style: Apply updated Prettier styles
If you need to rebase work past this style change, do as follows:
0. Consider this to be commit `commitA`, replacing that with its id in the following.
1. To make sure mistakes aren't fatal, assign a second branch to your current work.
2. Rebase your branch on the commit immediately before this one, commitA~
3. Run the following command at the root of the repo:
git rebase --strategy-option=theirs \
--exec 'npx prettier --write . && git add -u && git commit --amend --no-edit' \
commitA
That will take a short while esp. if you have multiple commits,
as it runs Prettier on everything for every commit.
If you've deleted files, the rebase may drop down to interactive mode
and have you `git rm` as appropriate, then `git rebase --continue`.
You should end up with just your changes in your branch,
prettily formatted. To validate that,
apply the same Prettier config change to your original branch,
reformat the files with `npm run prettier`,
and then compare the results with the rebased branch.
* chore: Clean up lint configs
2022-03-03 11:46:35 +03:00
|
|
|
/* eslint-env node */
|
|
|
|
|
|
2018-01-18 00:45:21 +03:00
|
|
|
module.exports = {
|
|
|
|
|
extends: ['eslint:recommended', 'plugin:react/recommended'],
|
|
|
|
|
env: {
|
2018-01-23 01:43:54 +03:00
|
|
|
es6: true,
|
2018-01-18 00:45:21 +03:00
|
|
|
browser: true,
|
2018-07-18 12:39:52 +03:00
|
|
|
jest: true,
|
2018-01-18 00:45:21 +03:00
|
|
|
},
|
2021-03-17 20:18:09 +03:00
|
|
|
parser: '@babel/eslint-parser',
|
2018-01-18 00:45:21 +03:00
|
|
|
parserOptions: {
|
2018-01-23 01:43:54 +03:00
|
|
|
ecmaVersion: 2017,
|
2018-01-18 00:45:21 +03:00
|
|
|
ecmaFeatures: {
|
|
|
|
|
jsx: true,
|
2018-01-23 01:43:54 +03:00
|
|
|
experimentalObjectRestSpread: true,
|
2018-01-18 00:45:21 +03:00
|
|
|
},
|
|
|
|
|
sourceType: 'module',
|
|
|
|
|
babelOptions: {
|
2019-09-24 18:38:21 +03:00
|
|
|
presets: ['@babel/preset-react'],
|
2018-01-18 00:45:21 +03:00
|
|
|
},
|
2022-02-16 17:47:32 +03:00
|
|
|
requireConfigFile: false,
|
Set `tabWidth: 2` in Prettier config (#2438)
* chore: Update Prettier config, setting tabWidth:2
* style: Apply updated Prettier styles
If you need to rebase work past this style change, do as follows:
0. Consider this to be commit `commitA`, replacing that with its id in the following.
1. To make sure mistakes aren't fatal, assign a second branch to your current work.
2. Rebase your branch on the commit immediately before this one, commitA~
3. Run the following command at the root of the repo:
git rebase --strategy-option=theirs \
--exec 'npx prettier --write . && git add -u && git commit --amend --no-edit' \
commitA
That will take a short while esp. if you have multiple commits,
as it runs Prettier on everything for every commit.
If you've deleted files, the rebase may drop down to interactive mode
and have you `git rm` as appropriate, then `git rebase --continue`.
You should end up with just your changes in your branch,
prettily formatted. To validate that,
apply the same Prettier config change to your original branch,
reformat the files with `npm run prettier`,
and then compare the results with the rebased branch.
* chore: Clean up lint configs
2022-03-03 11:46:35 +03:00
|
|
|
},
|
2018-01-18 00:45:21 +03:00
|
|
|
globals: {
|
|
|
|
|
gettext: false,
|
|
|
|
|
ngettext: false,
|
|
|
|
|
interpolate: false,
|
|
|
|
|
l: false,
|
|
|
|
|
expect: false,
|
|
|
|
|
test: false,
|
|
|
|
|
browser: false,
|
|
|
|
|
jest: false,
|
|
|
|
|
Promise: false,
|
2018-01-23 01:43:54 +03:00
|
|
|
Set: false,
|
|
|
|
|
URLSearchParameters: false,
|
|
|
|
|
FormData: false,
|
2018-01-18 00:45:21 +03:00
|
|
|
require: false,
|
|
|
|
|
shortcut: false,
|
|
|
|
|
sorttable: false,
|
|
|
|
|
$: false,
|
|
|
|
|
Pontoon: false,
|
2018-02-10 12:49:45 +03:00
|
|
|
jQuery: false,
|
|
|
|
|
Clipboard: false,
|
2020-12-21 23:42:50 +03:00
|
|
|
Chart: false,
|
2018-02-10 12:49:45 +03:00
|
|
|
NProgress: false,
|
|
|
|
|
diff_match_patch: false,
|
|
|
|
|
Highcharts: false,
|
2018-07-31 19:34:39 +03:00
|
|
|
Sideshow: false,
|
2018-03-01 19:26:39 +03:00
|
|
|
editor: false,
|
|
|
|
|
DIFF_INSERT: false,
|
|
|
|
|
DIFF_EQUAL: false,
|
2018-03-12 15:34:58 +03:00
|
|
|
DIFF_DELETE: false,
|
2018-08-07 14:05:12 +03:00
|
|
|
ga: false,
|
2018-02-10 12:49:45 +03:00
|
|
|
process: false,
|
2018-10-01 13:52:20 +03:00
|
|
|
generalShortcutsHandler: true,
|
|
|
|
|
traversalShortcutsHandler: true,
|
|
|
|
|
editorShortcutsHandler: true,
|
Set `tabWidth: 2` in Prettier config (#2438)
* chore: Update Prettier config, setting tabWidth:2
* style: Apply updated Prettier styles
If you need to rebase work past this style change, do as follows:
0. Consider this to be commit `commitA`, replacing that with its id in the following.
1. To make sure mistakes aren't fatal, assign a second branch to your current work.
2. Rebase your branch on the commit immediately before this one, commitA~
3. Run the following command at the root of the repo:
git rebase --strategy-option=theirs \
--exec 'npx prettier --write . && git add -u && git commit --amend --no-edit' \
commitA
That will take a short while esp. if you have multiple commits,
as it runs Prettier on everything for every commit.
If you've deleted files, the rebase may drop down to interactive mode
and have you `git rm` as appropriate, then `git rebase --continue`.
You should end up with just your changes in your branch,
prettily formatted. To validate that,
apply the same Prettier config change to your original branch,
reformat the files with `npm run prettier`,
and then compare the results with the rebased branch.
* chore: Clean up lint configs
2022-03-03 11:46:35 +03:00
|
|
|
},
|
2018-01-18 00:45:21 +03:00
|
|
|
plugins: ['react'],
|
Set `tabWidth: 2` in Prettier config (#2438)
* chore: Update Prettier config, setting tabWidth:2
* style: Apply updated Prettier styles
If you need to rebase work past this style change, do as follows:
0. Consider this to be commit `commitA`, replacing that with its id in the following.
1. To make sure mistakes aren't fatal, assign a second branch to your current work.
2. Rebase your branch on the commit immediately before this one, commitA~
3. Run the following command at the root of the repo:
git rebase --strategy-option=theirs \
--exec 'npx prettier --write . && git add -u && git commit --amend --no-edit' \
commitA
That will take a short while esp. if you have multiple commits,
as it runs Prettier on everything for every commit.
If you've deleted files, the rebase may drop down to interactive mode
and have you `git rm` as appropriate, then `git rebase --continue`.
You should end up with just your changes in your branch,
prettily formatted. To validate that,
apply the same Prettier config change to your original branch,
reformat the files with `npm run prettier`,
and then compare the results with the rebased branch.
* chore: Clean up lint configs
2022-03-03 11:46:35 +03:00
|
|
|
rules: {
|
2022-04-25 18:16:01 +03:00
|
|
|
curly: 'error',
|
2019-04-09 15:29:27 +03:00
|
|
|
'react/display-name': 0,
|
2019-01-15 19:04:03 +03:00
|
|
|
'react/prefer-es6-class': 1,
|
2018-08-30 10:22:24 +03:00
|
|
|
'react/prefer-stateless-function': 0,
|
2018-01-18 00:45:21 +03:00
|
|
|
'react/prop-types': 0,
|
|
|
|
|
'react/jsx-key': 0,
|
|
|
|
|
'react/jsx-uses-react': 1,
|
|
|
|
|
'react/jsx-uses-vars': 1,
|
2018-01-23 01:43:54 +03:00
|
|
|
'no-unused-vars': [
|
2018-01-18 00:45:21 +03:00
|
|
|
'error',
|
2018-01-23 01:43:54 +03:00
|
|
|
{ vars: 'all', args: 'after-used', ignoreRestSiblings: true },
|
2018-01-18 00:45:21 +03:00
|
|
|
],
|
2018-08-07 14:05:12 +03:00
|
|
|
'no-console': 1,
|
2024-03-04 15:02:13 +03:00
|
|
|
'no-var': 'error',
|
|
|
|
|
'prefer-const': [
|
|
|
|
|
'error',
|
|
|
|
|
{
|
|
|
|
|
destructuring: 'any',
|
|
|
|
|
ignoreReadBeforeAssign: false,
|
|
|
|
|
},
|
|
|
|
|
],
|
Set `tabWidth: 2` in Prettier config (#2438)
* chore: Update Prettier config, setting tabWidth:2
* style: Apply updated Prettier styles
If you need to rebase work past this style change, do as follows:
0. Consider this to be commit `commitA`, replacing that with its id in the following.
1. To make sure mistakes aren't fatal, assign a second branch to your current work.
2. Rebase your branch on the commit immediately before this one, commitA~
3. Run the following command at the root of the repo:
git rebase --strategy-option=theirs \
--exec 'npx prettier --write . && git add -u && git commit --amend --no-edit' \
commitA
That will take a short while esp. if you have multiple commits,
as it runs Prettier on everything for every commit.
If you've deleted files, the rebase may drop down to interactive mode
and have you `git rm` as appropriate, then `git rebase --continue`.
You should end up with just your changes in your branch,
prettily formatted. To validate that,
apply the same Prettier config change to your original branch,
reformat the files with `npm run prettier`,
and then compare the results with the rebased branch.
* chore: Clean up lint configs
2022-03-03 11:46:35 +03:00
|
|
|
},
|
2021-03-17 20:18:09 +03:00
|
|
|
settings: {
|
Set `tabWidth: 2` in Prettier config (#2438)
* chore: Update Prettier config, setting tabWidth:2
* style: Apply updated Prettier styles
If you need to rebase work past this style change, do as follows:
0. Consider this to be commit `commitA`, replacing that with its id in the following.
1. To make sure mistakes aren't fatal, assign a second branch to your current work.
2. Rebase your branch on the commit immediately before this one, commitA~
3. Run the following command at the root of the repo:
git rebase --strategy-option=theirs \
--exec 'npx prettier --write . && git add -u && git commit --amend --no-edit' \
commitA
That will take a short while esp. if you have multiple commits,
as it runs Prettier on everything for every commit.
If you've deleted files, the rebase may drop down to interactive mode
and have you `git rm` as appropriate, then `git rebase --continue`.
You should end up with just your changes in your branch,
prettily formatted. To validate that,
apply the same Prettier config change to your original branch,
reformat the files with `npm run prettier`,
and then compare the results with the rebased branch.
* chore: Clean up lint configs
2022-03-03 11:46:35 +03:00
|
|
|
react: {
|
2021-03-17 20:18:09 +03:00
|
|
|
version: 'detect',
|
2018-01-18 00:45:21 +03:00
|
|
|
},
|
2021-03-17 20:18:09 +03:00
|
|
|
},
|
2018-01-18 00:45:21 +03:00
|
|
|
};
|
