Restrictions for openType
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- api, documentation
Research direction
Start with the issue text and review the linked Microsoft Graph extensions plan proposal.docx for the intended distinction between customer-defined open types and unschematized service responses. Update the API guidelines so the recommendation and distinction are explicit; done means the guidance reflects both cases without ambiguity.
Written by the indexing model from the issue text.
Description
Add strong recommendation to avoid openType and consider Microsoft Graph extensions plan proposal.docx
Comment: we made the distinction between using an open type where customers could add custom properties (which was the original intent of open types) versus defining a type as open for cases where the service wanted to return unschematized properties (i.e., because they didn't want to commit to a specific set of properties).
- 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 ·
All issues in microsoft/api-guidelines
Similar issues
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
debpalash/VoiceStudio#2624 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
router-for-me/CLIProxyAPI#6399 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
ReactionMechanismGenerator/ARC#1067 ·
Maintainers usually reply within 1 day