[Blazor] PersistentState design question

[AndreiGorlov]

@AndreiGorlov thanks for contacting us.

This is by design, CascadingParameters and other form of parameters (which PersistentComponentState is a form of) must be public properties.

Originally posted by @javiercn in #63268

Property marked with [CascadingParameter] does not have to be public. Attribute works fine with private/protected properties.

[PersistentState], on the other hand, applicable to public props only. What is the rationale behind this design?
I just want to persist component state. Why do I have to expose it?

[MihuBot]

I'm a bot. Here is a possible related and/or duplicate issue (I may be wrong):

• PersistentState attribute throws InvalidOperationException at runtime when used with private property #62859

[javiercn]

@AndreiGorlov thanks for contacting us.

Most parts of the framework resort to requiring public properties for reflection, it impacts things like our ability to trim things correctly or our ability to perform source generation in the future instead of reflection.

[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.