- Fork this repo.
- Clone your fork into your
~/code/labs
folder.
Upon completion, run the following commands:
$ git add .
$ git commit -m"done"
$ git push origin master
Navigate to your repo and create a Pull Request -from your master branch to the original repository master branch.
In the Pull Request name, add your Campus, name, and the last name separated by a dash "-".
We learned how to use Mongoose to create Schemas and then interact with our MongoDB database. In the following exercise, we will practice how to implement this, creating awesome recipes.
The recipes.js
file already connects to the recipesApp database. Now we need to create a Recipe
Schema. The schema should have the following fields:
- title. Type
String
. It should be required and unique. - level. Type
String
. Only can be one of the following values: Easy Peasy - Amateur Chef - UltraPro Chef (remember the ENUM 😉) - ingredients. Type
Array
. - cousine. Type
String
. Should be required. - dishType. Type
String
. Possible values: Breakfast - Dish - Snack - Drink - Dessert - Other. - image. Type
String
. Default value: https://images.media-allrecipes.com/images/75131.jpg. - duration. Type
Number
. Min value should be 0. - creator. Type
String
- created. Type
Date
. By default today.
Using the Model.create
method, you should pass the info to create a new recipe. After the creation, you can use MongoDB Compass to check everything goes ok. After inserting the recipe, you should console.log
the title
of the recipe.
:::info
To run your code remember you should use $ node recipes.js
.
:::
Form the data.js
file we are importing an array of recipes. Using the Model.insertMany
method, you should add the entire array to the database. After inserting the elements, print on the console the title of each recipe.
Now you should have six different recipes in the database, but there was a mistake in one of them. The Rigatoni alla Genovese does not take that long. You should update the duration
field and set it to 100. After updating it, print a success message!
Oh oh! The Carrot Cake
is no longer available, so we need to remove it from the database. Using the Model.remove
method, remove that recipe from the database and display a success message after doing it!
After doing all the task you should close the database. Otherwise, the connection will keep open. Be careful about the asynchrony of all process; you should close it after everything is done! 😉