apiary

API Guidance does not explain the term `workload`. Although, it refers to that term several times - https://github.com/search?q=repo%3Amicrosoft%2Fapi-guidelines%20workload&type=code There is a need to explain the context of this term using...

Corrected RFC reference. Replaced RFC7230 with RFC7231

Ability to suppress rules inline

2

### Request: Suppress Specific Rule on a Case-by-Case Basis While managing a large portfolio of OpenAPI specifications, some APIs may have existed for years and belong to deprecated yet supported...

There are 100s of operations declaring `2XX` as HTTP response code. The value `2XX` is not a valid HTTP code. It must be actual number. Ref: * https://swagger.io/specification/#patterned-fields-1 * https://swagger.io/docs/specification/v3_0/describing-responses/#:~:text=Media%20Types.-,HTTP%20Status%20Codes,-Under%20responses%2C%20each...

There are 100s of unused or orphaned component definitions found in [openapi.yaml](https://github.com/microsoftgraph/msgraph-metadata/blob/master/openapi/v1.0/openapi.yaml). It’s good contract hygiene to prune anything that isn’t used, out of it. Here are some of the...

Enhanced the guidance for HTTP response code

1

This pull request updates the Microsoft Graph API guidelines to provide clearer guidance on HTTP response codes and error handling. The changes include a detailed table of recommended HTTP response...

Microsoft API Guidelines needs an update to clarify the Permissive-In / Strict-Out naming policy for API request and response. https://github.com/microsoft/api-guidelines/blob/vNext/graph/GuidelinesGraph.md#naming Add a section under Naming Conventions Input/Output Handling Recommend that...