From fdc9b8b60de6460b265197d315884a8e5fb20cee Mon Sep 17 00:00:00 2001 From: matthieu Date: Tue, 24 Mar 2026 21:54:23 +0100 Subject: [PATCH] fix : use correct useToast() API in export handler Co-Authored-By: Claude Opus 4.6 (1M context) --- frontend/pages/time-tracking.vue | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/frontend/pages/time-tracking.vue b/frontend/pages/time-tracking.vue index c5078f5..edc2958 100644 --- a/frontend/pages/time-tracking.vue +++ b/frontend/pages/time-tracking.vue @@ -325,10 +325,10 @@ async function onExport(params: { client?: number tags?: number[] }) { - const { success, error } = useToast() + const toast = useToast() const { t } = useNuxtApp().$i18n as { t: (key: string) => string } - success(t('timeEntries.exportLoading')) + toast.info({ message: t('timeEntries.exportLoading') }) try { const result = await timeEntryService.downloadExport(params) @@ -342,9 +342,9 @@ async function onExport(params: { document.body.removeChild(a) URL.revokeObjectURL(url) - success(t('timeEntries.exportSuccess')) + toast.success({ message: t('timeEntries.exportSuccess') }) } catch { - error(t('timeEntries.exportError')) + toast.error({ message: t('timeEntries.exportError') }) } }