Log errors when regenerating all component bridges

Without this change if you run regenerate-all-component-bridges and one
of the files causes an error, that will stop execution immediately. This
CL means the rest of the component bridges will still be regenerated,
and we'll log out the error for the component that caused the problem.

Change-Id: I26627f0836f7684bb28d45ea50ff19ef692e98dd
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2354097
Commit-Queue: Jack Franklin <jacktfranklin@chromium.org>
Commit-Queue: Alex Rudenko <alexrudenko@chromium.org>
Auto-Submit: Jack Franklin <jacktfranklin@chromium.org>
Reviewed-by: Alex Rudenko <alexrudenko@chromium.org>
This commit is contained in:
Jack Franklin
2020-08-13 13:38:20 +00:00
committed by Commit Bot
parent 13cf53581a
commit f20a184a01
@@ -14,7 +14,11 @@ const regenerateBridge = (pathToBridge: string) => {
throw new Error(`Could not find source file ${sourceFile}`);
}
main([sourceFile, ...process.argv.slice(2)]);
try {
main([sourceFile, ...process.argv.slice(2)]);
} catch (e) {
console.error(`ERROR regenerating bridge: ${e.message}`);
}
};
const excludedDirectories = new Set([path.resolve(path.join(process.cwd(), 'front_end', 'third_party'))]);