|
1 | 1 | # JavaScript - III |
2 | 2 |
|
| 3 | +Jose Montero Jr |
| 4 | + |
3 | 5 | This challenge focuses on using the `this` keyword as well as getting comfortable with prototypes by building out a fantasy themed video game. |
4 | 6 |
|
5 | 7 | ## Set Up The Project With Git |
6 | 8 |
|
7 | 9 | **Follow these steps to set up and work on your project:** |
8 | 10 |
|
9 | | -* [ ] Create a forked copy of this project. |
10 | | -* [ ] Add your project manager as collaborator on Github. |
11 | | -* [ ] Clone your OWN version of the repository (Not Lambda's by mistake!). |
12 | | -* [ ] Create a new branch: git checkout -b `<firstName-lastName>`. |
13 | | -* [ ] Implement the project on your newly created `<firstName-lastName>` branch, committing changes regularly. |
14 | | -* [ ] Push commits: git push origin `<firstName-lastName>`. |
| 11 | +- [x] Create a forked copy of this project. |
| 12 | +- [x] Add your project manager as collaborator on Github. |
| 13 | +- [x] Clone your OWN version of the repository (Not Lambda's by mistake!). |
| 14 | +- [x] Create a new branch: git checkout -b `<firstName-lastName>`. |
| 15 | +- [x] Implement the project on your newly created `<firstName-lastName>` branch, committing changes regularly. |
| 16 | +- [x] Push commits: git push origin `<firstName-lastName>`. |
15 | 17 |
|
16 | 18 | **Follow these steps for completing your project.** |
17 | 19 |
|
18 | | -* [ ] Submit a Pull-Request to merge <firstName-lastName> Branch into master (student's Repo). **Please don't merge your own pull request** |
19 | | -* [ ] Add your project manager as a reviewer on the pull-request |
20 | | -* [ ] Your project manager will count the project as complete by merging the branch back into master. |
| 20 | +- [x] Submit a Pull-Request to merge <firstName-lastName> Branch into master (student's Repo). **Please don't merge your own pull request** |
| 21 | +- [x] Add your project manager as a reviewer on the pull-request |
| 22 | +- [x] Your project manager will count the project as complete by merging the branch back into master. |
21 | 23 |
|
22 | 24 | ## Assignment Set Up |
23 | 25 |
|
24 | | -* Complete all the exercises as described inside each assignment file. |
25 | | -* To test your `console.log()` statements, open up the index.html file found in the assignments folder and use the developer tools to view the console. |
| 26 | +- Complete all the exercises as described inside each assignment file. |
| 27 | +- To test your `console.log()` statements, open up the index.html file found in the assignments folder and use the developer tools to view the console. |
26 | 28 |
|
27 | 29 | ## The `this` keyword |
28 | 30 |
|
29 | 31 | Having a solid understanding of how `this` works will give you a huge advantage when you start building with more advanced frameworks. Use the [this.js](assignments/this.js) file to traverse through a few `this` problems. |
30 | 32 |
|
31 | 33 | ## Prototype |
32 | 34 |
|
33 | | -The prototype challenge will focus on building prototypes for a fantasy themed game that includes mages, swordsmen, and archers. Follow the [prototypes.js](assignments/this.js) instructions closely to create the beginnings of what could be an awesome JavaScript game. |
| 35 | +The prototype challenge will focus on building prototypes for a fantasy themed game that includes mages, swordsmen, and archers. Follow the [prototypes.js](assignments/this.js) instructions closely to create the beginnings of what could be an awesome JavaScript game. |
34 | 36 |
|
35 | | -* Read the instructions found within the file carefully to finish the challenges. |
36 | | -* Remember to un-comment the objects and console logs to test your work at the bottom of the page. |
| 37 | +- Read the instructions found within the file carefully to finish the challenges. |
| 38 | +- Remember to un-comment the objects and console logs to test your work at the bottom of the page. |
0 commit comments