- Work in a fork of this repository
- Work in a branch on your fork
- Write all of your code in a directory named
lab-+<your name>e.g.lab-susan - Open a pull request to this repository
- Submit on canvas a question and observation, how long you spent, and a link to your pull request
Configure the root of your repository with the following files and directories. Thoughtfully name and organize any additional configuration or module files.
- README.md - contains documentation
- .gitignore - contains a robust
.gitignorefile - .eslintrc - contains the course linter configuratoin
- .eslintignore - contains the course linter ignore configuration
- package.json - contains npm package config
- create a
lintscript for running eslint - create a
startscript for running your server - create a
testscript for running your tests
- create a
- server.js - runs your application
- model/ - contains mongoose schemas
- route/ - contains your routes
- lib/ - contains custom middleware and helpers
- __test__/ - contains route tests
- continue working on the express and mongoDB API that you started yesterday
- include an additional resource that contains a "relationship" to the single resource that has already been created - if you used a "list", you may not use "notes"
- create GET, POST, PUT, and DELETE routes for your newly added resource
- use
populatein the logic of your GET route to/api/new-resource-name/:idin order to populate your related resource with actual data (ex:List.findById(req.params.id).populate('notes'))
