Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[3.25.1] Svelte messes up my $session in Sapper #5439

Closed
Evertt opened this issue Sep 22, 2020 · 3 comments
Closed

[3.25.1] Svelte messes up my $session in Sapper #5439

Evertt opened this issue Sep 22, 2020 · 3 comments

Comments

@Evertt
Copy link

Evertt commented Sep 22, 2020

Honestly I don't know what Svelte is doing exactly, but I tried and this bug only happens in 3.25.1 and not in 3.25.0.

I can only tell you what I see. Normally in my sapper app I use $session store which at the moment always only consists of 2 items: { csrfToken: "a random string...", user: { /* a user object */ }}.

Now for some reason, in version 3.25.1, $session gets messed up and csrfToken is gone and user is now the root object. It's like svelte did $session = $session.user somewhere...

And it must have happened somewhere between these 2 commits.

@tanhauhau
Copy link
Member

It feels it's similar to #5437

@Evertt
Copy link
Author

Evertt commented Sep 22, 2020

Probably yes.

@Conduitry
Copy link
Member

Yes, duplicate of #5412, already fixed on master, will be fixed in the next version of Svelte

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants