api-guidelines
api-guidelines copied to clipboard
microsoft
Microsoft REST API Guidelines
The current guidance does not pass the schema validation. I have updated it to reflect what actually passes schema validation (except for a single suppression that is required). You can...
Porting [this](https://dev.azure.com/msazure/One/_git/AD-AggregatorService-Wiki/pullrequest/5809345?_a=files&path=/API/Design/Modeling-patterns/Value-Based-Property-Validity.md) PR from the old repo.
Add strong recommendation to avoid openType and consider [Microsoft Graph extensions plan proposal.docx](https://microsoft-my.sharepoint-df.com/:w:/p/dkershaw/EYOFKrcI4-hHj_jBcdL0iuIBLZEl3q6tEKo01I4nebyXsg?e=MYJS97) Comment: we made the distinction between using an open type where customers could add custom properties (which...
Discussed previously, this PR adds the guidance to avoid the filter-as-segment OData feature and instead use a composable function which accepts an expression parameter for those scenarios where operations on...
Adding the guidance pattern according to [this](https://microsoft.sharepoint.com/teams/APICouncil/_layouts/15/Doc.aspx?sourcedoc=%7B3569deb7-5543-404f-99b0-70554b7f8778%7D&action=edit&wd=target(ADRs.one%7C0edc1435-5069-4f42-8318-bf31c71c4e37%2FADR-024%20Using%20functions%20as%20query%20parameter%20aliases%7Ce157a2d9-7960-4f08-b0da-8e22ac5248c6%2F)&wdorigin=NavigationUrl&share=IgG33mk1Q1VPQJmwcFVLf4d4AQ7bKVE-D30Of6JCTvaTqbc) ADR. The pattern is to use OData functions as "aliases" for the more complicated or common OData query options for robust APIs that...
