The purpose of this diagnostic is to determine whether you can identify the
value of this when invoked in differenct contexts.
- Fork and clone this repository.
- Change into the new directory.
- Install dependencies.
- Create and checkout a new branch, named
response. - Follow the directions given in diagnostic.md.
- 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 assessment. For example:
Comfort: 3
Clarity: 3
I used Google and my class notes to help with this assessment.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.
Note: For this diagnostic, grunt nag will complain about example code we
have provided for the questions. You are not required to fix this warnings. Only
fix warnings that occur on lines you have written for your response.
Source code distributed under the MIT license. Text and other assets copyright General Assembly, Inc., all rights reserved.