Mittwoch, 18. Mai, 2016

Finishing Angular TODO application and deploying to production 115
95 next();
96 };
This, rather nicely structured, mumbo jumbo explained per functions:
• getErrorMessage - iterates over the Mongoose errors and returns the first one
• create
– creates a new Todo model instance using the HTTP request body
– adds the authenticated Passport user as the todo creator
– saves the todo document using Mongoose instance save method
• list
– fetches the collection of todo documents by using the Mongoose instance find method
– sorts them by created property
– adds name and _username_fields to to the creator property
• read - outputs the todo object as JSON
• todoById- fetches the todo document by using the Mongoose instance findById method.
• update - updates the todo document which you’ve previously fetched with the todoById
middleware (if you remeber middlewares that is, if not, please go and refresh your memory
in the second tutorial which was all about Node.js and Express²⁰²)
• delete - deletes the todo document which you’ve previously fetched with the todoById
middleware
• hasAuthorization - middleware that uses the req.todo and req.user objects to verify that the
current user is the creator of the current todo.
To continue you need to say the magic word
You need to know which user is authenticated so that you know which one made a certain action
(like for example created a new todo). You can check this inside every method, but that’s just code
duplication since you can use the Express middleware chaining to block unauthorized requests from
executing your controller methods.
So, in the app/controllers/users.server.controller.js file add the following code:
²⁰²https://hackhands.com/delving-node-js-express-web-framework/