The details of this project are outlined in the project spec.
- Within your group, decide on one person to have the project repository on their Github account. This person will fork this repository - on the top right corner of the page, click the fork button.
- Both group members should then clone down the forked repository (make sure that everyone is added as a collaborator as well). Since you don't want your project to be named "whats-cookin-starter-kit", add an optional argument after the repo url when cloning. The command should look like this:
git clone [remote-address] [what you want to name the repo]. - Once you have cloned the repo, change into the directory and install the project dependencies. Run npm install to install project dependencies.
- Run open src/index.html in the terminal to see the HTML page (you should see some boilerplate HTML displayed on the page)
- Make sure both members of your team are collaborators on the forked repo.
There is no boilerplate for testing in this starter-kit repo. You will need to set this up yourself. However, if you ran npm install, then the tooling you need to start testing is already installed (mocha and chai).
Run the command in your terminal npm run lint to run the linter on your JavaScript code. There will be errors and warnings right from the start in this starter kit, but that's ok - the linter is still running successfully.
Your linter will look only at the JavaScript files you have within the src and the test directories.
{
"id": [number],
"name": [string],
"pantry": [array of objects with amount and ingredient id properties]
},{
"ingredients" [array of objects with ingredients ids(connection to ingredients), ingredient names, and quantity data],
"instructions": [array of objects with instructions properties and numbered steps],
"name": [string],
"tags": [array of strings representing info about the recipes]
}{
"estimatedCostInCents": [number],
"id": [number -- connection to users and recipes],
"name": [string]
}