Persist state from Static Server Rendering (SSR) to Interactive islands

[Johnlockk]

Is there an existing issue for this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

Hello,

i've searched for a solution but i didn't understand if anything has been implemented yet.
I have a Blazor Web App composed of two SSR Components, login and logout (to handle Cookie authentication) ,while the rest of components are all on InteractiveServer render mode.
During the login procedure i'm receiving an access token from a secured endpoint to be used for the subsequent API calls on Interactive components. Is there any way to persist the token or any other user data while switching from SSR to InteractiveServer?

Similar to #47796 and #50741, not sure if any action has been taken.

Thank you

Describe the solution you'd like

It would be great to have a transparent and flexible mechanism to persiste state from SSR to Interactive islands

Additional context

No response

[javiercn]

@Johnlockk thanks for contacting us.

This is already possible with PersistentComponentState. See https://learn.microsoft.com/en-us/aspnet/core/blazor/components/prerender?view=aspnetcore-9.0#persist-prerendered-state

[Johnlockk]

@javiercn Thank you...it seems that navigating away from the SSR component is not storing the state for the next Interactive component, not sure if this is by design. ApplicationState seems to be reinitialized and the TryTakeFromJson call returns a null value. Is PersistentComponentState only useful to maintain the state in case of prerendering? Thanks

[dotnet-policy-service]

This issue has been resolved and has not had any activity for 1 day. It will be closed for housekeeping purposes.

See our Issue Management Policies for more information.