Work around types in test code -- if we really want to do this, we sh…

…ould have a formal interface extension

client/src/components/Common/ExportForm.test.ts

@@ -43,7 +43,10 @@ describe("ExportForm.vue", () => {
 
     it("should localize button text", async () => {
         const newLocal = wrapper.find(".export-button").text();
-        expect(newLocal).toBeLocalizationOf("Export");
+        // TODO: fix typing, this is a jest matcher with a custom expect
+        // extension, or, just use vanilla javascript in test harness if there
+        // isn't significant value in typing here?
+        (expect(newLocal) as any).toBeLocalizationOf("Export");
     });
 
     it("should emit 'export' event with correct inputs on export button click", async () => {

client/src/components/User/UserDeletion.test.ts

@@ -23,6 +23,7 @@ describe("UserDeletion.vue", () => {
     it("contains a localized link", async () => {
         const wrapper = mountComponent();
         const el = await wrapper.find(ROOT_COMPONENT.preferences.delete_account.selector);
-        expect(el.text()).toBeLocalizationOf("Delete Account");
+        // todo: fix typing, see note in ExportForm.test.ts
+        (expect(el.text()) as any).toBeLocalizationOf("Delete Account");
     });
 });

client/tests/jest/helpers.js

@@ -8,7 +8,7 @@ import { iconPlugin } from "components/plugins/icons";
 import { localizationPlugin } from "components/plugins/localization";
 import { vueRxShortcutPlugin } from "components/plugins/vueRxShortcuts";
 import { PiniaVuePlugin } from "pinia";
-import { fromEventPattern,timer } from "rxjs";
+import { fromEventPattern, timer } from "rxjs";
 import { debounceTime, take, takeUntil } from "rxjs/operators";
 import _l from "utils/localization";
 import Vuex from "vuex";