Refactor/#108-Use promise to use .catch statement

[ryumy97]

.save() and .find() is async function. We want to use Promise to handle these operations

resolves #108

• The pull request is complete according to the following criteria:
  • Acceptance criteria have been met
  • The documentation is kept up-to-date
  • Comprehensive tests (if applicable) have been generated and all pass.
  • The pull request describes the changes that have been made, and enough information is present in the description for any developer to understand what has changed
  • Commits have been squashed (or will be on merge).
  • The branch name is descriptive and follows the pull request title format : {issue/bug...}/(Issue Number) - Name of issue. E.g bug/30-Fix-Project
  • The pull request title is of the following format : {issue/bug...}/(Issue Number) - Name of issue. E.g bug/30-Fix-Project
  • The description uses github syntax to link to the issue. E,g Resolves se701g2/Doto#{Number}
  • At least two reviewers assigned. One of which must be the assigner of the issue.
  • If there are merge conflicts, run git rebase as opposed to git merge with master.

[tnzhu]

@Cvos0162 Heya, backend is working on this, so I don't think this will go through.

[ryumy97]

@Cvos0162 Heya, backend is working on this, so I don't think this will go through.

Oh, that's cool. I was just passing by and thought this was good coding practice.
Anyway, the issue is still valid since there are no changes in the code. Please make sure to reference the issue #108 on the new PR, when someone actually handles them.
(Although I think, there is no reason to pick this PR up, but that's ok)

[res550]

Hey @Cvos0162 and @tnzhu whats the status for the other can we close this one

[tnzhu]

Hey @Cvos0162 and @tnzhu whats the status for the other can we close this one

Yeah, I think the plan is to refactor once all changes are made.

[res550]

Okay cool that sounds good