Ready

[s18v]

My app is complete @codepathreview @codepath

[codepathreview]

:+1: nice work. With this assignment, we've now explored all the main components for building REST APIs! If this were 2009, you would be well on your way to building most developer APIs that you could find published. Over the next few weeks, we'll be focusing on realtime APIs, tooling and production deployments, the last pieces in your arsenal for distributing your own enterprise APIs.

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 interacting with multiple 3rd-party APIs, requests should alway be made in parallel when possible, and streaming JSON parsing should be utilized to minimize parsing overhead.
• All posts in the timeline should be consistent across social networks with the same data fields shown for each in addition to a label with logo specifying the origin network.
• When a new social network is authorized, post for that network should be included immediately within the timeline.