sync: move try-catch out of needsSyncing and handle errors it in full…

…Sync

The motivation for this is bitwarden/cli#129
where failed sync's are swallowed by try-catch. By moving the try-catch
to the outside it is possible to reuse the already existing
allowThrowOnError argument which callers can use to signal whether
fullSync should throw or ignore errors silently. This patch is
companioned with a patch to the SyncCommand CLI command to pass
allowThrowOnError.

src/services/sync.service.ts

@@ -76,12 +76,11 @@ export class SyncService implements SyncServiceAbstraction {
         }
 
         const now = new Date();
-        const needsSyncResult = await this.needsSyncing(forceSync);
-        const needsSync = needsSyncResult[0];
-        const skipped = needsSyncResult[1];
-
-        if (skipped) {
-            return this.syncCompleted(false);
+        var needsSync = false;
+        try {
+            needsSync = await this.needsSyncing(forceSync);
+        } catch (e) {
+            if (allowThrowOnError) { throw e; }
         }
 
         if (!needsSync) {
@@ -226,23 +225,19 @@ export class SyncService implements SyncServiceAbstraction {
 
     private async needsSyncing(forceSync: boolean) {
         if (forceSync) {
-            return [true, false];
+            return true;
         }
 
         const lastSync = await this.getLastSync();
         if (lastSync == null || lastSync.getTime() === 0) {
-            return [true, false];
+            return true;
         }
 
-        try {
-            const response = await this.apiService.getAccountRevisionDate();
-            if (new Date(response) <= lastSync) {
-                return [false, false];
-            }
-            return [true, false];
-        } catch (e) {
-            return [false, true];
+        const response = await this.apiService.getAccountRevisionDate();
+        if (new Date(response) <= lastSync) {
+            return false;
         }
+        return true;
     }
 
     private async syncProfile(response: ProfileResponse) {