feat(tools): remove eslint-plugin-prettier for prettier (freeCodeCamp#42438)

* feat: remove eslint-plugin-prettier for prettier

This removes the annoying lint warnings when all that needs to change is
formatting

* fix: use .js lint-staged config to ignore properly

* fix: lint everything if a lot of files are changed

It's faster than making lots of individual linter calls

* chore: apply prettier

* fix: ignore code in curriculum-file-structure

Author: ojeytonwilliams

.eslintrc-base.json

@@ -131,7 +131,6 @@
     "operator-assignment": 0,
     "padded-blocks": 0,
     "prefer-object-spread/prefer-object-spread": 2,
-    "prettier/prettier": "error",
     "quote-props": [2, "as-needed"],
     "quotes": [2, "single", "avoid-escape"],
     "radix": 2,

.eslintrc.json

@@ -10,15 +10,14 @@
   "root": true,
   "extends": [
     "./.eslintrc-base.json",
-    "plugin:prettier/recommended",
     "plugin:import/typescript",
-    "plugin:jsx-a11y/recommended"
+    "plugin:jsx-a11y/recommended",
+    "prettier"
   ],
   "plugins": [
     "react",
     "import",
     "prefer-object-spread",
-    "prettier",
     "react-hooks",
     "jsx-a11y",
     "jest-dom",
@@ -58,7 +57,10 @@
       "plugins": ["@typescript-eslint"]
     },
     {
-      "files": ["./tools/ui-components/**/*.test.[jt]s?(x)", "./client/**/*.test.[jt]s?(x)"],
+      "files": [
+        "./tools/ui-components/**/*.test.[jt]s?(x)",
+        "./client/**/*.test.[jt]s?(x)"
+      ],
       "extends": ["plugin:testing-library/react", "plugin:jest-dom/recommended"]
     },
     {

.github/labeler.yml

@@ -1,22 +1,22 @@
-"scope: docs":
+'scope: docs':
   - docs/**/*
 
-"scope: curriculum":
+'scope: curriculum':
   - curriculum/challenges/**/*
 
-"platform: client":
+'platform: client':
   - client/**/*
 
-"platform: api":
+'platform: api':
   - api-server/**/*
 
-"scope: tools/scripts":
+'scope: tools/scripts':
   - cypress/**/*
   - tools/**/*
   - .github/**/*
   - utils/**/*
 
-"scope: i18n":
+'scope: i18n':
   - any: ['curriculum/challenges/**/*', '!curriculum/challenges/english/**/*']
   - docs/i18n/**/*
   - client/i18n/**/*

.github/workflows/autoclose.yml

@@ -2,9 +2,9 @@ name: Autoclose
 on:
   pull_request_target:
     branches:
-      - "main"
+      - 'main'
     paths:
-      - ".gitignore"
+      - '.gitignore'
 
 jobs:
   autoclose:

.github/workflows/codeql-analysis.yml

@@ -1,4 +1,4 @@
-name: "CodeQL"
+name: 'CodeQL'
 
 on:
   push:
@@ -14,7 +14,7 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        language: ["javascript"]
+        language: ['javascript']
     steps:
       - name: Checkout repository
         uses: actions/checkout@v2

.github/workflows/crowdin-i18n-client-ui-upload.yml

@@ -3,7 +3,7 @@ on:
   workflow_dispatch:
   schedule:
     # runs everyday at 11:15 AM UTC
-    - cron: "15 11 * * *"
+    - cron: '15 11 * * *'
 
 jobs:
   i18n-upload-client-ui-files:

.github/workflows/crowdin-i18n-curriculum-download.yml

@@ -56,7 +56,6 @@ jobs:
           CROWDIN_PROJECT_ID: ${{ secrets.CROWDIN_PROJECT_ID_CURRICULUM }}
           CROWDIN_PERSONAL_TOKEN: ${{ secrets.CROWDIN_CAMPERBOT_SERVICE_TOKEN }}
 
-
       # Convert Simplified Chinese to Traditional #
       - name: Generate Translations
         uses: ./tools/crowdin/actions/convert-chinese

.github/workflows/crowdin-i18n-curriculum-upload.yml

@@ -3,7 +3,7 @@ on:
   workflow_dispatch:
   schedule:
     # runs everyday at 11:30 AM UTC
-    - cron: "30 11 * * *"
+    - cron: '30 11 * * *'
 
 jobs:
   i18n-upload-curriculum-files:

.github/workflows/crowdin-i18n-docs-upload.yml

@@ -3,7 +3,7 @@ on:
   workflow_dispatch:
   schedule:
     # runs everyday at 11:00 AM UTC
-    - cron: "0 11 * * *"
+    - cron: '0 11 * * *'
 
 jobs:
   i18n-upload-docs-files:

.github/workflows/cypress.yml

@@ -53,7 +53,6 @@ jobs:
           name: webpack-stats
           path: client/public/stats.json
 
-
   cypress-run:
     name: Test
     runs-on: ubuntu-18.04

.github/workflows/labeler.yaml

@@ -1,12 +1,12 @@
-name: "Pull Request Labeler"
+name: 'Pull Request Labeler'
 on:
-- pull_request_target
+  - pull_request_target
 
 jobs:
   triage:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/labeler@v3
-      with:
-        repo-token: "${{ secrets.GITHUB_TOKEN }}"
-        sync-labels: true
+      - uses: actions/labeler@v3
+        with:
+          repo-token: '${{ secrets.GITHUB_TOKEN }}'
+          sync-labels: true

.lintstagedrc.js

@@ -0,0 +1,28 @@
+const { ESLint } = require('eslint');
+
+const cli = new ESLint();
+
+// if a lot of files are changed, it's faster to run prettier/eslint on the
+// whole project than to run them on each file separately
+module.exports = {
+  '*.(js|ts|tsx)': files =>
+    files.length > 10
+      ? ['eslint --max-warnings=0 --cache --fix .', 'prettier --write .']
+      : [
+          'eslint --max-warnings=0 --cache --fix ' +
+            files.filter(file => !cli.isPathIgnored(file)).join(' '),
+          ...files.map(filename => `prettier --write '${filename}'`)
+        ],
+  '*.!(js|ts|tsx)': files =>
+    files.length > 10
+      ? 'prettier --write .'
+      : files.map(
+          filename => `prettier --write --ignore-unknown '${filename}'`
+        ),
+  './curriculum/challenges/**/*.md': files =>
+    files.length > 10
+      ? 'npm run lint:challenges'
+      : files.map(
+          filename => `node ./tools/scripts/lint/index.js '${filename}'`
+        )
+};

.prettierignore

@@ -1,6 +1,9 @@
 **/.cache
 **/public
 client/static
-fixtures
+**/*fixtures*
 curriculum/challenges/_meta/*/*
 curriculum/challenges/**/*
+config/**/*.json
+client/i18n/**/*.json
+docs/i18n

CODE_OF_CONDUCT.md

@@ -1,2 +1 @@
-
 > Our Code of Conduct is available here: <https://www.freecodecamp.org/code-of-conduct/>

CONTRIBUTING.md

@@ -1,3 +1,3 @@
 ## Our contributing docs are available here: <https://contribute.freecodecamp.org>.
 
-Looking to edit these docs? Read [this document](https://contribute.freecodecamp.org/#/how-to-work-on-the-docs-theme) first.
+Looking to edit these docs? Read [this document](https://contribute.freecodecamp.org/#/how-to-work-on-the-docs-theme) first.

HoF.md

@@ -4,4 +4,4 @@ We appreciate any responsible disclosure of vulnerabilities that might impact th
 
 - Mehul Mohan from [codedamn](https://codedamn.com) ([@mehulmpt](https://twitter.com/mehulmpt)) - [Vulnerability Fix](https://github.com/freeCodeCamp/freeCodeCamp/blob/bb5a9e815313f1f7c91338e171bfe5acb8f3e346/client/src/components/Flash/index.js)
 - Peter Samir https://www.linkedin.com/in/peter-samir/
-> ### Thank you for your contributions :pray:
+  > ### Thank you for your contributions :pray:

LICENSE.md

@@ -6,14 +6,14 @@ All rights reserved.
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions are met:
 
-* Redistributions of source code must retain the above copyright notice, this
+- Redistributions of source code must retain the above copyright notice, this
   list of conditions and the following disclaimer.
 
-* Redistributions in binary form must reproduce the above copyright notice,
+- Redistributions in binary form must reproduce the above copyright notice,
   this list of conditions and the following disclaimer in the documentation
   and/or other materials provided with the distribution.
 
-* Neither the name of the copyright holder nor the names of its
+- Neither the name of the copyright holder nor the names of its
   contributors may be used to endorse or promote products derived from
   this software without specific prior written permission.
 

api-server/.babelrc

@@ -2,9 +2,11 @@
   "presets": [
     [
       "@babel/preset-env",
-      {"targets": {
-        "node": 10
-      }}
+      {
+        "targets": {
+          "node": 10
+        }
+      }
     ]
   ],
   "plugins": [

api-server/src/common/index.less

@@ -1 +1,3 @@
-&{ @import "./app/index.less"; }
+& {
+  @import './app/index.less';
+}

api-server/src/common/models/user.json

@@ -276,9 +276,7 @@
       "default": {}
     },
     "donationEmails": {
-      "type": [
-        "string"
-      ]
+      "type": ["string"]
     },
     "isDonating": {
       "type": "boolean",

client/package.json

@@ -25,10 +25,6 @@
     "clean": "gatsby clean",
     "predevelop": "node ../tools/scripts/build/ensure-env.js && npm run build:workers -- --env development",
     "develop": "node --max_old_space_size=4000 node_modules/gatsby-cli develop --inspect=9230",
-    "format": "npm run format:gatsby && npm run format:src && npm run format:utils",
-    "format:gatsby": "prettier-eslint --write --trailing-comma none --single-quote './gatsby-*.js'",
-    "format:src": "prettier-eslint --write --trailing-comma none --single-quote './src/**/*.js'",
-    "format:utils": "prettier-eslint --write --trailing-comma none --single-quote './utils/**/*.js'",
     "lint": "node ./i18n/schema-validation.js",
     "serve": "gatsby serve -p 8000",
     "serve-ci": "serve -l 8000 -c ../serve.json public",

client/src/pages/learn/back-end-development-and-apis/back-end-development-and-apis-projects/index.md

@@ -3,15 +3,17 @@ title: Introduction to the Back End Development and APIs Projects
 block: Back End Development and APIs Projects
 superBlock: Back End Development and APIs
 ---
+
 ## Introduction to the Back End Development and APIs Projects
 
 Time to put your newly learnt skills to work! By working on projects you would have the opportunity of applying all the skills, principles and concepts you have learnt so far including npm packages, basic Node, basic Express, MongoDB, and Mongoose.
 
 In this section you get the chance to:
- * Build a Timestamp Microservice
- * Build a Request Header Parser Microservice
- * Build a URL Shortener Microservice
- * Build a Exercise Tracker
- * Build a File Metadata Microservice
+
+- Build a Timestamp Microservice
+- Build a Request Header Parser Microservice
+- Build a URL Shortener Microservice
+- Build a Exercise Tracker
+- Build a File Metadata Microservice
 
 By the end of this, you would have 5 microservices under your belt that you can show off to friends, family, employers, etc. Have fun and remember to use the [Read-Search-Ask](https://forum.freecodecamp.org/t/how-to-get-help-when-you-are-stuck-coding/19514) method if you get stuck.

client/src/pages/learn/back-end-development-and-apis/index.md

@@ -2,6 +2,7 @@
 title: Back End Development and APIs
 superBlock: back-end-development-and-apis
 ---
+
 ## Introduction to Back End Development and APIs
 
 This is a stub introduction for Back End Development and APIs
@@ -19,7 +20,8 @@ A monolith typically has the three key components of any application - the UI, B
 To overcome some of the issues, one of the suggestions that was made early on was to functionally decompose an application, referred to as the Scale Cube in the book [The Art of Scalability](www.theartofscalability.com). This eventually led to the microservices pattern that we see now. A microservice takes a single bit of functionality and bundles all the layers of technology into it. This means that each microservice has its own UI, business logic and data store. To deliver a larger piece of functionality, microservices talk to one another through common communication methods like APIs or messages.
 
 ## Key benefits
-1. Microservices can be developed and deployed independently of one another, thereby reducing the risk of one wrong piece of code  bringing down an entire application 
+
+1. Microservices can be developed and deployed independently of one another, thereby reducing the risk of one wrong piece of code bringing down an entire application
 2. Easier to isolate and find where issues lie, while debugging
 3. Fits the modern DevOps paradigm, as the architecture is well placed for Continuous Integration/Continuous Deployment
 4. Enables developers to choose a language and data store technology best suited for that bit of functionality
@@ -28,13 +30,15 @@ To overcome some of the issues, one of the suggestions that was made early on wa
 7. Easy to change, as it encapsulates a single piece of business functionality
 
 ## Key drawbacks
+
 1. Additional operational overheads to monitor and manage multiple services
 2. Manage communications between services
 3. Additional effort to build fault tolerance
 4. Getting the right balance of functional and data separation is not easy
 5. Distributed transaction model comes with its own share of issues regarding data consistency (eventual consistency)
 
 ### Sources
+
 1. Microservices, a definition - by Martin Fowler and James Lewis : https://www.martinfowler.com/articles/microservices.html
 2. Introduction to Microservices - NGINX blog : https://www.nginx.com/blog/introduction-to-microservices/
 3. What are microservices - Smartbear : https://smartbear.com/learn/api-design/what-are-microservices/

client/src/pages/learn/coding-interview-prep/algorithms/index.md

@@ -3,6 +3,7 @@ title: Introduction to the Coding Interview Algorithms
 block: Algorithms
 superBlock: Coding Interview Prep
 ---
+
 ## Introduction to the Coding Interview Prep Algorithms
 
 These challenges are meant to teach and challenge you with common algorithms that you will encounter in real life. These challenges will be a great learning experience to help improve your programming and logical skills.

client/src/pages/learn/coding-interview-prep/data-structures/index.md

@@ -3,6 +3,7 @@ title: Introduction to the Coding Interview Data Structure Questions
 block: Data Structures
 superBlock: Coding Interview Prep
 ---
+
 ## Introduction to the Coding Interview Data Structure Questions
 
-These excercises are meant to help you deal with large or complex data by using many different data types other than your standard objects or arrays. 
+These excercises are meant to help you deal with large or complex data by using many different data types other than your standard objects or arrays.

client/src/pages/learn/coding-interview-prep/project-euler/index.md

@@ -3,12 +3,13 @@ title: Introduction to the Project Euler Problems
 block: Project Euler
 superBlock: Coding Interview Prep
 ---
+
 ## Introduction to the Project Euler Problems
 
 [Project Euler](https://projecteuler.net/) (pronounced Oiler) is a series of challenging mathematical/computer programming problems meant to delve into unfamiliar areas and learn new concepts in a fun and recreational manner.
 
->The problems range in difficulty and for many the experience is inductive chain learning. That is, by solving one problem it will expose you to a new concept that allows you to undertake a previously inaccessible problem. 
+> The problems range in difficulty and for many the experience is inductive chain learning. That is, by solving one problem it will expose you to a new concept that allows you to undertake a previously inaccessible problem.
 >
 > Although mathematics will help you arrive at elegant and efficient methods, the use of a computer and programming skills will be required to solve most problems.
 >
->_from the Project Euler <a href='https://projecteuler.net/' rel='noopener noreferrer'>home page</a>_
+> _from the Project Euler <a href='https://projecteuler.net/' rel='noopener noreferrer'>home page</a>_

client/src/pages/learn/coding-interview-prep/rosetta-code/index.md

@@ -3,7 +3,9 @@ title: Introduction to the Rosetta Code Problems
 block: Rosetta Code
 superBlock: Coding Interview Prep
 ---
+
 ## Introduction to the Rosetta Code Problems
 
 [The Rosetta Code](https://rosettacode.org) is a list of programming challenges which will help you build your programming skills.
->"The idea is to present solutions to the same task in as many different languages as possible, to demonstrate how languages are similar and different, and to aid a person with a grounding in one approach to a problem in learning another." - _Homepage of the Rosetta Code site_
+
+> "The idea is to present solutions to the same task in as many different languages as possible, to demonstrate how languages are similar and different, and to aid a person with a grounding in one approach to a problem in learning another." - _Homepage of the Rosetta Code site_

client/src/pages/learn/coding-interview-prep/take-home-projects/index.md

@@ -3,16 +3,18 @@ title: Introduction to the Coding Interview Take Home Projects
 block: Take Home Projects
 superBlock: Coding Interview Prep
 ---
+
 ## Introduction to the Coding Interview Take Home Projects
 
 Programming interviews have always been stressful. One of the solutions is giving the applicant a take home project to be completed outside of the interview. These types of interviews usually require a lot of work, but they're a great way for employers to see how you might perform on the job.
 
 The interview after the project submission could be a discussion about the applicant’s design decisions, scalability, and what the applicant might have done differently. This approach is more effective when the applicant doesn’t have a lot of publicly available past projects.
 
 In this section you get the chance to work on many Take Home Projects like:
-*  Show Local Weather using Weather API and Geolocation
-*  Build a Wikipedia Viewer using Wikipedia's API
-*  Build a Pinterest Clone using Masonry.js library 
-and many more!
+
+- Show Local Weather using Weather API and Geolocation
+- Build a Wikipedia Viewer using Wikipedia's API
+- Build a Pinterest Clone using Masonry.js library
+  and many more!
 
 By the end of this section, you will have plenty of Take Home Projects under your belt. This will boost your confidence and prepare you for Take Home Project Interviews. Have fun and remember to use the [Read-Search-Ask](https://forum.freecodecamp.org/t/how-to-get-help-when-you-are-stuck/19514) method if you get stuck.