Challenge Overview
Cloud Hub has been working with Swagger since the beginning of our API project, and we really love the module and what it adds to for documentation and validation. One issue we can't seem to quite figure out is how to better handle errors that happen outside of a normal API call. Throwing a new error or unhandled exception is swallowed up by bag pipes and we don't have a good way to get those messages out to our error monitoring service. We have some ideas, but this challenge will be a little open to how we solve this issue. We are going to share more techincal details in the forums.
2. Please include a git patch for easier integration of changes.
3. The bulk of your documentation should be in the Readme.md and you should assume that this will be open source so make sure you cover all the steps to set up, If you have specific information that should not be included in a public readme (like links to your video) put them in a file called submission.txt and they will be omitted from the project if it is open sourced.
4. If you are creating or modifying SQL files, do not user table abbreviations.
Final Submission Guidelines
1. Any additions or modifications to the code project pass on "npm run lint". Any modifications to the base project needs to pass the tests, npm run test.2. Please include a git patch for easier integration of changes.
3. The bulk of your documentation should be in the Readme.md and you should assume that this will be open source so make sure you cover all the steps to set up, If you have specific information that should not be included in a public readme (like links to your video) put them in a file called submission.txt and they will be omitted from the project if it is open sourced.
4. If you are creating or modifying SQL files, do not user table abbreviations.