gaspersic/freeCodeCamp
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

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

Browse Source 
* 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
This commit is contained in:
Oliver Eyton-Williams
2021-10-06 17:32:21 +02:00
committed by GitHub
parent 8518079316
commit c8d7f0a782
152 changed files with 905 additions and 735 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/how-to-work-on-coding-challenges.md
View File

@ -287,7 +287,7 @@ Challenges should have the minimum number of tests necessary to verify that a ca
Our goal is to communicate the single point that the challenge is trying to teach, and test that they have understood that point.
Challenge tests can make use of the Node.js and Chai.js assertion libraries. Also, if needed, user-generated code can be accessed in the `code` variable. In addition, the `__helpers` object exposes several functions that simplify the process of writing tests. The available functions are defined in _client/src/utils/curriculum-helpers.ts_.
Challenge tests can make use of the Node.js and Chai.js assertion libraries. Also, if needed, user-generated code can be accessed in the `code` variable. In addition, the `__helpers` object exposes several functions that simplify the process of writing tests. The available functions are defined in _client/src/utils/curriculum-helpers.ts_.
## Formatting seed code