chore: fix violations from the newly-enabled unicorn rules

Apply the code changes required by the rules enabled in the previous
commit: String() coercions over template literals, location.assign over
href assignment, URL#href over toString, Object.entries/values loop
forms, and related autofixes. Disable unicorn/no-non-function-verb-prefix,
and disable unicorn/no-error-property-assignment for test files.

Assisted-by: claude-code:opus-4.8
This commit is contained in:
silverwind committed 2026-06-17 07:00:36 +02:00
1 parent 668d95a602
commit 767ed117e2
41 files changed
+81 -103

No files matched your search

+1 -1
View File
@@ -50,7 +50,7 @@ export class UserEventsSharedWorker {
// * in this case, the logout fetch call already completes and has sent the "logout" message to the worker
// * there can be a data-race between the fetch call's redirection and the "logout" message from the worker
// * the fetch call's logout redirection should always win over the worker message, because it might have a custom location
setTimeout(() => { window.location.href = `${appSubUrl}/` }, 1000);
setTimeout(() => { window.location.assign(`${appSubUrl}/`) }, 1000);
} else if (event.data.type === 'close') {
this.sharedWorker.port.postMessage({type: 'close'});
this.sharedWorker.port.close();