Fix cache updating of creating new issue

emilgoldsmith commented 5 years ago

Related Issue

Description

There was a typo which made the cache not update correctly (wouldn't have happened with Typescript!), and also added some catch statements. Our promise code is really bad at the moment :'(

How Has This Been Tested?

Screenshots (if appropriate):

Checklist:

[ ] My code follows the code style of this project. (see the style guide)
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] Coveralls reported increased code coverage, and full coverage for all the code I added / changed (or I have a good reason that I explained above for why this is not the case)

emilgoldsmith commented 5 years ago

I'm going to merge this as soon as CI passes, can't wait for review cycle right now as we got to deploy

coveralls commented 5 years ago

Coverage remained the same at 6.258% when pulling d88a54b8914e0e90235ae33102b8bc7a27c504a8 on fix-add-issue-cache into 8e12b421fe10eaa9ee0c72f867d8ee43053f272f on master.

thegazelle-ad / gazelle-server