Why doesn't supabase auth set cookies??
I'm having to rewrite my Sveltekit app to accommodate the new SvelteKit changes and trying to make my app more SSRed.
I've had to jump through some painful hoops to get the cookies ('sb-access-token' and 'sb-refresh-token') set and unset for the auth changes in my MagicLink auth .... and this still requires me using frontend code to handle the response and then trigger POSTs and stuff to get the cookies saved.
Wondering ... why does Supabase auth not just set the cookies on the response in the 'Set-Cookie' header?
Would save me a tonne of headache and means I wouldn't have to use
I've had to jump through some painful hoops to get the cookies ('sb-access-token' and 'sb-refresh-token') set and unset for the auth changes in my MagicLink auth .... and this still requires me using frontend code to handle the response and then trigger POSTs and stuff to get the cookies saved.
Wondering ... why does Supabase auth not just set the cookies on the response in the 'Set-Cookie' header?
Would save me a tonne of headache and means I wouldn't have to use
onAuthStateChange and handle all the cases ... and would also mean it doesn't get triggered everytime I move away from the tab and back again (which annoyingly forces a refreshed signin)