Shared Type Design Pattern

Assessment

This issue has not been assessed yet.

Description

Contributor guide

Open the contributing guide

First steps

1. Read the whole issue, then the project's contributing guide.
2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
3. Fork the repository and make your change on a branch.
4. Open a pull request that references the issue number.

More from microsoft/api-guidelines

• Clarify Permissive-In / Strict-Out Naming Policy in Guidelines Open

  Difficulty 1/5 1-3 hours Newbie friendliness 68/100

  microsoft/api-guidelines#571 · Opened Jul 31, 2025

• Resource Provider Guidance Needed for Capacity Exhaustion and Capacity-Constrained Responses Open

  Difficulty 4/5 3-5 days Newbie friendliness 45/100

  microsoft/api-guidelines#595 · 1 comment · Opened Sep 23, 2026

• Issue: All down your Review Page is unanswered and unsatisfied Customers. Open

  Difficulty 5/5 Over a week Newbie friendliness 5/100

  microsoft/api-guidelines#570 · Opened Jul 2, 2025

• Im Open

  Difficulty 5/5 Over a week Newbie friendliness 10/100

  microsoft/api-guidelines#562 · Opened Oct 5, 2024

• Continue with the team Open

  Difficulty 5/5 Over a week Newbie friendliness 1/100

  microsoft/api-guidelines#560 · Opened Sep 9, 2024

All issues in microsoft/api-guidelines