Codepath - Assignment 2 - Blogger

[umkatakam]

My app is complete. //cc @codepathreview @codepath

List of features are detailed in the readme.

Please LMK what you think. Had a busy week could only finish the required features. Shall work and submit optional features and refactor the code into individual routes in couple of days.

Mahesh

[umkatakam]

Created an additional PR with some code clean up. https://github.com/umkatakam/blogger/pull/2 Since I did this after submission deadline. Haven't merged it and created it as a PR.

[codepathreview]

:+1: nice work. The goal of this assignment was to learn how to implement local authentication, interact with a data store, and render a webUI. In addition, you explored using middleware to facilitate common HTTP functionality. Over the next few weeks, we'll be focusing on more complex integrations and realtime functionality that we find in modern APIs and web apps.

Here's a checklist of things that I'm looking for in this project. You should review the checklist, and make any changes to your project, if necessary.

• Review the properties and methods that you've made available through your various module.exports. Your modules should reveal the minimum interface and only expose things that must be used by other modules.
• There should be no *Sync calls anywhere in your code, and no require calls except at the top of each module file.
• All required dependencies should be declared in the package.json "dependencies". When installing dependencies, use the --save option: npm install --save somepackage.
• Keep your code DRY by refactoring all code interacting with req or res into a reusable composable middleware: (req, res, next)=>{}.
• Your Models should exist each in their own module file, and Mongo embedded objects should have their own Schema. It is okay to include an embedded object's schema in the same file if it's not used in other schemas.
• Be sure to validate all user inputs. First, through strict enforcements in your data schemas, and second in your user, post and comment creation routes. Never rely solely on your schema for validation.
• All routes requiring a user account should enforce authentication through the isLoggedIn or equivalent route middleware: app.post('/post/:postId', isLoggedIn, ...)
• When handling user authentication data, security is paramount. Never store plain-text passwords anywhere, and always be sure to use at least a global salt (pepper) when hashing.