• JavaScript Objects Modeling
• JavaScript Objects: Referencing Own Properties
• JavaScript Constructors
• JavaScript Prototypes

1. Fork and clone this repository.
2. Change into the new directory.
3. Create a new branch, named response.
4. Checkout the response branch.
5. Install dependencies by running npm install
6. Follow the directions given in lib/diagnostic.js.
7. Check your responses by running grunt test.
8. Before the alotted time is up, push to your fork and issue a pull request.

Your pull request description should contain a "fist to five" for comfort and clarity. Additionally, you should mention the resources you used to help you complete this diagnostic. For example:

Comfort: 3
Clarity: 3

I used Google and my class notes to help with this diagnostic.

You may wish to refer to "How do I submit diagnostics?" and other FAQs related to forking, cloning, and pull requests.

You may use any resource other than each other to complete this diagnostic. This includes referencing talk materials, appropriate documentation, and searching for help online.

You should be running grunt nag before diagnosing any bugs, since it finds some of the most common sources of errors. After grunt nag passes, you should run grunt test to run the included tests. Tests will tell you whether of not your responses are correct.

1. All content is licensed under a CC­BY­NC­SA 4.0 license.
2. All software code is licensed under GNU GPLv3. For commercial use or alternative licensing, please contact [email protected].