Complex type pattern
@corranrogue9 is already working on this.
Since Aug 9, 2023.
Assessment
This issue has not been assessed yet.
Description
Clarify when to group stuff in a complex type
- Dominant language
- No language data
- Stars
- 23.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/api-guidelines
-
Clarify Permissive-In / Strict-Out Naming Policy in GuidelinesPossibly taken @Rohan5commit claimed this 162 days ago. Open
Difficulty 1/5 1-3 hours Newbie friendliness 68/100
microsoft/api-guidelines#571 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
microsoft/api-guidelines#595 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
microsoft/api-guidelines#589 ·
-
Difficulty 5/5 Over a week Newbie friendliness 5/100
microsoft/api-guidelines#570 ·
-
ImOpen
Difficulty 5/5 Over a week Newbie friendliness 10/100
microsoft/api-guidelines#562 ·