A few edit suggestions

[BillWagner]

Type of issue

Typo

Description

This article should start with auto-implemented properties for init only properties. From there, it should discuss field-backed properties, and finish with any properties with a hand-coded backing field.

Page URL

https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/keywords/init

Content source URL

https://github.com/dotnet/docs/blob/main/docs/csharp/language-reference/keywords/init.md

Document Version Independent Id

fc780319-a7fd-d9d1-1877-638ac05eb5f4

Article author

@BillWagner

Metadata

• ID: 816634c5-6e7d-3845-f9a3-1ce305fea838
• Service: dotnet-csharp
• Sub-service: lang-reference

[baonguyen2310]

@BillWagner

I'm reviewing this issue and need some clarification:

1. The issue suggests reorganizing the content in this order:

   • Auto-implemented properties
   • Field-backed properties
   • Properties with hand-coded backing field

2. However, the current article only contains:

   • Auto-implemented properties
   • Field-backed properties (with regular backing fields)

3. Questions:

   • Should we add a new section about "Properties with hand-coded backing field"?
   • If yes, could you provide specific examples of what should be included in this section?

This will help me better understand the scope of changes needed.

[BillWagner]

Hi @baonguyen2310

I wrote this issue for me to remember when I added content for the field backed properties feature. I'm working on this now (see #43261). That's why the issue references content that didn't yet exist. The term "field backed property" is a property where the property accessors uses the new keyword field to access the compiler generated backing field for an automatically implemented property.

We're glad that you want to contribute to our repo. Our normal practice is that we assign issues only when we are actively working on them, or have it in our near term plan.

When you're looking for issues to contribute to, you can expect that no one is working on any issues that are unassigned. If any of those interest you, add a comment and we'll watch for the PR, or assign the issue to you so no one else starts working on it.

[baonguyen2310]

Hi @BillWagner,

Thank you for the clarification!

I'll keep an eye on unassigned issues and am happy to contribute where I can.

Thanks again!