Problems when subscribing to flash store and hovering over <a> tag where load function uses redirect. about sveltekit-flash-message

[ciscoheat]

Thanks for understanding, I'll reopen this until I've fixed the docs!

[ciscoheat]

Since Svelte preloads the links, this is expected. You can modify that behavior with these options: https://kit.svelte.dev/docs/link-options

[hansaskov]

Thank you. You are correct that changing the data-sveltekit-preload-data attribute to be tap instead of hover does fix this issue.

Do you think it is possible to not set the flash-message if the preload page is not navigated to?

[ciscoheat]

Not unless there is a way to detect if a link is preloading through the RequestEvent, and I don't think there is.

[hansaskov]

I have figured out a workaround, that i believe makes sense. The idea is to store the url pathname we expect to navigate to within the flash-message, then only trigger the Toast if the expected url pathname matches the pages pathname.

Example

Start by updating the flash message to include the expected pathname we navigate to.

// app.d.ts
declare namespace App {
	interface PageData {
		flash?: {
			type: 'success' | 'error';
			message: string;
			pathname: string;  // Update here
		};
	}
}

When we try to navigate to the /private page, we redirected to the homepage with the message of "Message from /private" as well as the pathname of the page we expect to redirect to.

// src/routes/private/+page.server.ts
export const load: PageServerLoad = async (event) => {
	const message = { type: 'error', message: 'Message from /private', pathname: '/' } as const;
	throw redirect(303, message.pathname, message, event);
};

In the layout page we subscribe to the flash store, which will trigger each time the flash-message is updated. The code will make an early return if $flash is undefined or if the pathname of the current page is not the same as the expected pathname from the flash-message

// layout.svelte
import { getFlash } from 'sveltekit-flash-message/client';
import { page } from '$app/stores';

const flash = getFlash(page);

flash.subscribe(($flash) => {
	if (!$flash) return;
	if ($flash.pathname != $page.url.pathname) return;

	errorToast.message = $flash.message;
	toastStore.trigger(errorToast);

});;

You might have noticed that a small bug is still present with the above implementation. When hovering over the private page, then manually navigating to the homepage, the toast is incorrectly displayed. This can be fixed by only triggering the toast if the navigation was done using redirects. To implement this we can create the isGotoNavigated variable and subscribe it to the after navigate store to be true when the navigation was of type goto. Then return early if the navigation is not a redirect.

import { getFlash } from 'sveltekit-flash-message/client';
import { page } from '$app/stores';
import { afterNavigate } from '$app/navigation';

const flash = getFlash(page);

let isGotoNavigated = false;
afterNavigate(({type}) => {
	isGotoNavigated = ['goto'].includes(type as string); // is true when the navigation was a redirect
})

flash.subscribe(($flash) => {
	if (!$flash) return;
	if ($flash.pathname != $page.url.pathname) return;
	if (!isGotoNavigated) return;

	errorToast.message = $flash.message;
	toastStore.trigger(errorToast);
});

I would really love to see this implemented directly into the library as i believe it represents what most people expect when using the it for the first time.

I would like to hear your feedback on this, and if there are some downsides to this implementation. I also would like to contribute myself and put it under a settings flag. But that will be in a couple of days

[ciscoheat]

I'd like to keep things simple, so introducing an extra variable into the flash message isn't feasible as a requirement. Testing the type in afterNavigate isn't really optimal either since the cookie has already been set during the preload.

The only way to keep things simple would be to prevent the redirect (and hence the cookie) during the preload, but if it's not possible to detect preload in the load function, I'd rather add a note about data-sveltekit-preload-data in the docs.

[hansaskov]

That is totally understandable, preventing the redirect is the most elegant solution. And i think you are correct that differentiating between preloaded and non preloaded functions is non trivial.

I'm closing this issue, as it is intended behavior that can be mentioned in the docs.