mirror of
https://github.com/10h30/odin-javascript-exercises.git
synced 2026-06-05 15:09:09 +09:00
Update readme, add case-anything dep
This commit is contained in:
@@ -2,18 +2,16 @@
|
|||||||
|
|
||||||
These JavaScript exercises are intended to complement the JavaScript content on The Odin Project (TOP). They should only be done when instructed during the course of the curriculum.
|
These JavaScript exercises are intended to complement the JavaScript content on The Odin Project (TOP). They should only be done when instructed during the course of the curriculum.
|
||||||
|
|
||||||
**Note:** The `generator-exercise` file is not actually an exercise; it is a script that generates exercises. It was created to help efficiently write these exercises.
|
|
||||||
|
|
||||||
## Contributing
|
## Contributing
|
||||||
|
|
||||||
If you have a suggestion to improve an exercise, an idea for a new exercise, or notice an issue with an exercise, please feel free to open an issue after thoroughly reading our [contributing guide](https://github.com/TheOdinProject/.github/blob/main/CONTRIBUTING.md).
|
If you have a suggestion to improve an exercise, an idea for a new exercise, or notice an issue with an exercise, please feel free to open an issue after thoroughly reading our [contributing guide](https://github.com/TheOdinProject/.github/blob/main/CONTRIBUTING.md).
|
||||||
|
|
||||||
## How To Use These Exercises
|
## How To Use These Exercises
|
||||||
|
|
||||||
|
|
||||||
1. Fork and clone this repository. To learn how to fork a repository, see the GitHub documentation on how to [fork a repo](https://docs.github.com/en/get-started/quickstart/fork-a-repo).
|
1. Fork and clone this repository. To learn how to fork a repository, see the GitHub documentation on how to [fork a repo](https://docs.github.com/en/get-started/quickstart/fork-a-repo).
|
||||||
- Copies of repositories on your machine are called clones. If you need help cloning to your local environment you can learn how from the GitHub documentation on [cloning a repository](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository).
|
- Copies of repositories on your machine are called clones. If you need help cloning to your local environment you can learn how from the GitHub documentation on [cloning a repository](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository).
|
||||||
1. Before you start working on any exercises, you should first ensure you have the following installed:
|
1. Before you start working on any exercises, you should first ensure you have the following installed:
|
||||||
|
|
||||||
- **NPM**. You should have installed NPM already in our [Installing Node.js](https://www.theodinproject.com/paths/foundations/courses/foundations/lessons/installing-node-js) lesson. Just in case you need to check, type `npm --version` in your terminal. If you get back `Command 'npm' not found, but can be installed with:`, **do not follow the instructions in the terminal** to install with `apt-get` as this causes permission issues. Instead, go back to the installation lesson and install Node with NVM by following the instructions there.
|
- **NPM**. You should have installed NPM already in our [Installing Node.js](https://www.theodinproject.com/paths/foundations/courses/foundations/lessons/installing-node-js) lesson. Just in case you need to check, type `npm --version` in your terminal. If you get back `Command 'npm' not found, but can be installed with:`, **do not follow the instructions in the terminal** to install with `apt-get` as this causes permission issues. Instead, go back to the installation lesson and install Node with NVM by following the instructions there.
|
||||||
- **Jest**. After cloning this repository to your local machine and installing NPM, go into the newly created directory (`cd javascript-exercises`) and run `npm install`. This will install Jest and set up the testing platform based on our preconfigured settings. (Note: if you get warnings that packages are out of date or contain vulnerabilities, you can safely ignore them for these exercises.)
|
- **Jest**. After cloning this repository to your local machine and installing NPM, go into the newly created directory (`cd javascript-exercises`) and run `npm install`. This will install Jest and set up the testing platform based on our preconfigured settings. (Note: if you get warnings that packages are out of date or contain vulnerabilities, you can safely ignore them for these exercises.)
|
||||||
|
|
||||||
@@ -23,6 +21,7 @@ If you have a suggestion to improve an exercise, an idea for a new exercise, or
|
|||||||
- A `solutions` directory that contains a solution and the same test file with all of the tests unskipped.
|
- A `solutions` directory that contains a solution and the same test file with all of the tests unskipped.
|
||||||
|
|
||||||
To complete an exercise, you'll need to go to the exercise directory with `cd exerciseName` in the terminal and run `npm test exerciseName.spec.js`. This should run the test file and show you the output. When you first run a test, it will fail. This is by design! You must open the exercise file and write the code needed to get the test to pass.
|
To complete an exercise, you'll need to go to the exercise directory with `cd exerciseName` in the terminal and run `npm test exerciseName.spec.js`. This should run the test file and show you the output. When you first run a test, it will fail. This is by design! You must open the exercise file and write the code needed to get the test to pass.
|
||||||
|
|
||||||
1. Some of the exercises have test conditions defined in their spec file as `test.skip` compared to `test`. This is purposeful. After you pass one `test`, you will change the next `test.skip` to `test` and test your code again. You'll do this until all conditions are satisfied. **All tests must pass at the same time**, and you should not have any `test.skip` instances by the time you finish an exercise.
|
1. Some of the exercises have test conditions defined in their spec file as `test.skip` compared to `test`. This is purposeful. After you pass one `test`, you will change the next `test.skip` to `test` and test your code again. You'll do this until all conditions are satisfied. **All tests must pass at the same time**, and you should not have any `test.skip` instances by the time you finish an exercise.
|
||||||
1. Once you successfully finish an exercise, check the `solutions` directory within each exercise to compare it with yours.
|
1. Once you successfully finish an exercise, check the `solutions` directory within each exercise to compare it with yours.
|
||||||
- You should not be checking the solution for an exercise until you finish it!
|
- You should not be checking the solution for an exercise until you finish it!
|
||||||
@@ -36,3 +35,13 @@ The first exercise, `helloWorld`, will walk you through the process in-depth.
|
|||||||
## Debugging
|
## Debugging
|
||||||
|
|
||||||
To debug functions, you can run the tests in the Visual Studio Code debugger terminal. You can open this by clicking the "Run and Debug" icon on the left or pressing <kbd>Ctrl</kbd> + <kbd>Shift</kbd> + <kbd>D</kbd>, then clicking JavaScript Debug Terminal. You will be able to set breakpoints as you would in the Chrome DevTools debugger. You can run `npm test exerciseName.spec.js` to then execute your code up until your breakpoint and step through your code as necessary. **NOTE**: To take advantage of the debugger, you **MUST** run the script in the debugger terminal, not the bash or zsh terminal.
|
To debug functions, you can run the tests in the Visual Studio Code debugger terminal. You can open this by clicking the "Run and Debug" icon on the left or pressing <kbd>Ctrl</kbd> + <kbd>Shift</kbd> + <kbd>D</kbd>, then clicking JavaScript Debug Terminal. You will be able to set breakpoints as you would in the Chrome DevTools debugger. You can run `npm test exerciseName.spec.js` to then execute your code up until your breakpoint and step through your code as necessary. **NOTE**: To take advantage of the debugger, you **MUST** run the script in the debugger terminal, not the bash or zsh terminal.
|
||||||
|
|
||||||
|
## Adding a new exercise
|
||||||
|
|
||||||
|
To add a new exercise:
|
||||||
|
|
||||||
|
1. Be sure you've ran `npm install` at the root of the `javascript-exercises` directory
|
||||||
|
2. Run the command `npm run generate`
|
||||||
|
3. When prompted, enter the name of the new exercise in camelCase syntax
|
||||||
|
|
||||||
|
After entering an exercise name, a new directory with the necessary files will be created. You will then need to update the `README.md` and `spec.js` files as well as the files in the `solution` directory of the new exercise.
|
||||||
|
|||||||
Generated
+13
@@ -9,6 +9,7 @@
|
|||||||
"version": "1.0.0",
|
"version": "1.0.0",
|
||||||
"license": "ISC",
|
"license": "ISC",
|
||||||
"devDependencies": {
|
"devDependencies": {
|
||||||
|
"case-anything": "^2.1.13",
|
||||||
"eslint": "^8.47.0",
|
"eslint": "^8.47.0",
|
||||||
"eslint-config-airbnb-base": "^15.0.0",
|
"eslint-config-airbnb-base": "^15.0.0",
|
||||||
"eslint-plugin-import": "^2.28.1",
|
"eslint-plugin-import": "^2.28.1",
|
||||||
@@ -1962,6 +1963,18 @@
|
|||||||
"upper-case-first": "^2.0.2"
|
"upper-case-first": "^2.0.2"
|
||||||
}
|
}
|
||||||
},
|
},
|
||||||
|
"node_modules/case-anything": {
|
||||||
|
"version": "2.1.13",
|
||||||
|
"resolved": "https://registry.npmjs.org/case-anything/-/case-anything-2.1.13.tgz",
|
||||||
|
"integrity": "sha512-zlOQ80VrQ2Ue+ymH5OuM/DlDq64mEm+B9UTdHULv5osUMD6HalNTblf2b1u/m6QecjsnOkBpqVZ+XPwIVsy7Ng==",
|
||||||
|
"dev": true,
|
||||||
|
"engines": {
|
||||||
|
"node": ">=12.13"
|
||||||
|
},
|
||||||
|
"funding": {
|
||||||
|
"url": "https://github.com/sponsors/mesqueeb"
|
||||||
|
}
|
||||||
|
},
|
||||||
"node_modules/chalk": {
|
"node_modules/chalk": {
|
||||||
"version": "4.1.2",
|
"version": "4.1.2",
|
||||||
"resolved": "https://registry.npmjs.org/chalk/-/chalk-4.1.2.tgz",
|
"resolved": "https://registry.npmjs.org/chalk/-/chalk-4.1.2.tgz",
|
||||||
|
|||||||
@@ -14,6 +14,7 @@
|
|||||||
},
|
},
|
||||||
"homepage": "https://github.com/TheOdinProject/javascript-exercises#readme",
|
"homepage": "https://github.com/TheOdinProject/javascript-exercises#readme",
|
||||||
"devDependencies": {
|
"devDependencies": {
|
||||||
|
"case-anything": "^2.1.13",
|
||||||
"eslint": "^8.47.0",
|
"eslint": "^8.47.0",
|
||||||
"eslint-config-airbnb-base": "^15.0.0",
|
"eslint-config-airbnb-base": "^15.0.0",
|
||||||
"eslint-plugin-import": "^2.28.1",
|
"eslint-plugin-import": "^2.28.1",
|
||||||
|
|||||||
+4
-1
@@ -1,5 +1,6 @@
|
|||||||
const { mkdir } = require("fs/promises");
|
const { mkdir } = require("fs/promises");
|
||||||
const { join } = require("path");
|
const { join } = require("path");
|
||||||
|
const { camelCase } = require("case-anything");
|
||||||
const { createExerciseDirectoryName } = require("./generators/helpers");
|
const { createExerciseDirectoryName } = require("./generators/helpers");
|
||||||
const { writeReadme } = require("./generators/writeReadme");
|
const { writeReadme } = require("./generators/writeReadme");
|
||||||
const { writeExercise } = require("./generators/writeExercise");
|
const { writeExercise } = require("./generators/writeExercise");
|
||||||
@@ -14,14 +15,16 @@ module.exports = function (plop) {
|
|||||||
);
|
);
|
||||||
}
|
}
|
||||||
|
|
||||||
|
const camelExerciseName = camelCase(exerciseName);
|
||||||
const exerciseDirectoryName = await createExerciseDirectoryName(
|
const exerciseDirectoryName = await createExerciseDirectoryName(
|
||||||
exerciseName
|
camelExerciseName
|
||||||
);
|
);
|
||||||
const basePath = join("./", exerciseDirectoryName);
|
const basePath = join("./", exerciseDirectoryName);
|
||||||
const solutionPath = join(basePath, "solution");
|
const solutionPath = join(basePath, "solution");
|
||||||
|
|
||||||
await mkdir(basePath);
|
await mkdir(basePath);
|
||||||
await mkdir(solutionPath);
|
await mkdir(solutionPath);
|
||||||
|
|
||||||
await writeReadme(basePath);
|
await writeReadme(basePath);
|
||||||
await writeExercise(basePath);
|
await writeExercise(basePath);
|
||||||
await writeExercise(solutionPath);
|
await writeExercise(solutionPath);
|
||||||
|
|||||||
Reference in New Issue
Block a user