style: Use space after catch

We are currently inconsistent with whether or not to put a space
after catch clauses. While the predominant style is to omit it,
that's inconsistent with the style we use for any other statement.
There's not really a good reason to stick with it, so switch to
the style gjs/eslint default to.

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/607
This commit is contained in:
Florian Müllner
2019-01-29 02:26:39 +01:00
parent d008c6c5c5
commit f250643385
26 changed files with 53 additions and 53 deletions

View File

@ -64,7 +64,7 @@ function disableExtension(uuid) {
let uuid = orderReversed[i];
try {
ExtensionUtils.extensions[uuid].stateObj.disable();
} catch(e) {
} catch (e) {
logExtensionError(uuid, e);
}
}
@ -77,7 +77,7 @@ function disableExtension(uuid) {
try {
extension.stateObj.disable();
} catch(e) {
} catch (e) {
logExtensionError(uuid, e);
}
@ -85,7 +85,7 @@ function disableExtension(uuid) {
let uuid = order[i];
try {
ExtensionUtils.extensions[uuid].stateObj.enable();
} catch(e) {
} catch (e) {
logExtensionError(uuid, e);
}
}
@ -132,7 +132,7 @@ function enableExtension(uuid) {
extension.state = ExtensionState.ENABLED;
_signals.emit('extension-state-changed', extension);
return;
} catch(e) {
} catch (e) {
if (extension.stylesheet) {
theme.unload_stylesheet(extension.stylesheet);
delete extension.stylesheet;
@ -208,7 +208,7 @@ function reloadExtension(oldExtension) {
let newExtension;
try {
newExtension = ExtensionUtils.createExtensionObject(uuid, dir, type);
} catch(e) {
} catch (e) {
logExtensionError(uuid, e);
return;
}
@ -235,7 +235,7 @@ function initExtension(uuid) {
ExtensionUtils.installImporter(extension);
try {
extensionModule = extension.imports.extension;
} catch(e) {
} catch (e) {
logExtensionError(uuid, e);
return false;
}
@ -243,7 +243,7 @@ function initExtension(uuid) {
if (extensionModule.init) {
try {
extensionState = extensionModule.init(extension);
} catch(e) {
} catch (e) {
logExtensionError(uuid, e);
return false;
}