Skip to content

Clarify cascading params access modifiers #36297

@guardrex

Description

@guardrex

Description

I think the remark should be that private is recommended for components because the parameter should be scoped for use only in the component's class in most cases.

Also, I'll consistently use private in article examples and Blazor sample apps.

Page URL

https://learn.microsoft.com/en-us/aspnet/core/blazor/components/cascading-values-and-parameters?view=aspnetcore-9.0

Content source URL

https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/components/cascading-values-and-parameters.md

Document ID

5fe884b8-51e1-1b91-57f8-522ff0b7890c

Platform Id

e0f6ebc1-0472-3585-b7d2-e814f7abf701

Article author

@guardrex

Metadata

  • ID: 7e7ba96d-bae0-96ee-e76a-71c6e5f4c23f
  • PlatformId: e0f6ebc1-0472-3585-b7d2-e814f7abf701
  • Service: aspnet-core
  • Sub-service: blazor

Related Issues

Metadata

Metadata

Assignees

Type

No type

Projects

Status

P2 - Medium Priority

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions