Naming Convention

Open maximilianosilva opened this issue 4 months ago • 0 comments

Type of issue

Typo

Description

The convention suggests that private instance fields should start with an underscore, followed by camel casing for the rest of the name, such as _name instead of name. This helps improve code readability and maintainability.

While this example is perfectly functional, I just want to confirm: Is this an intentional exception to the standard naming convention rule

[Enter feedback here]

Page URL

https://learn.microsoft.com/en-us/dotnet/communitytoolkit/mvvm/generators/observableproperty?source=docs

Content source URL

https://github.com/MicrosoftDocs/CommunityToolkit/blob/main/docs/mvvm/generators/ObservableProperty.md

Document Version Independent Id

baa399f1-fe73-add4-df84-b99a29fb4083

Platform Id

ad393ed8-f5e6-db3a-482a-0d8a458e1b40

Article author

@Sergio0694

Metadata

ID: baa399f1-fe73-add4-df84-b99a29fb4083
PlatformId: ad393ed8-f5e6-db3a-482a-0d8a458e1b40
Service: dotnet-communitytoolkit
Sub-service: mvvm-toolkit

Oct 22 '25 17:10 maximilianosilva