valid-parameter-content-key
Overview
This rule belongs to the openapi-v3-syntax-linting ruleset and states that: 
Key of a parameter content map must be set as a specific media type which is in compliance with RFC6838.
| Property | Value | 
|---|---|
| Enabled | Yes | 
| Maximum Severity | Warning | 
| Message | The key of the parameter content map definition is invalid. | 
| Code | OPENAPI3SYNTAX_L040 | 
| Type | Linting | 
| Rule System | Syntax | 
| Broad Category | Parameters | 
| Products Impacted | API Transformer, Code Generation, Developer Experience Portal | 
| Tags | openapi3openapisyntaxlintingmedia typecontentparameter | 
Suggested Fixes
- A media type consists of a top-level type and a subtype, which is further structured into a tree. A media type can optionally define a suffix and parameters as well.
- A media type follows a pattern like the following where segments between [] are optional segments: <type>/[<tree>.]<subtype>[+<suffix>]*[;<parameter>]
- Some examples of valid media types are: application/json, application/vnd.api+json, text/plain.
For More Information
- https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#parameter-object
- https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#media-types
- https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.0.3.md#parameter-object
- https://www.rfc-editor.org/rfc/rfc6838
- https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.0.3.md#media-types
- https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.0.3.md#openapi-specification
- https://docs.apimatic.io/rulesets/overview/