schema-content-schema-only-for-strings
Overview
This rule belongs to the openapi-v3-standards-linting ruleset and states that: 
The property contentSchema can only be used for Schema Objects when the type is either unspecified (implying any type) or set as string. This property is not applicable for any other types.
| Property | Value | 
|---|---|
| Enabled | Yes | 
| Maximum Severity | Warning | 
| Message | Property contentSchemais not applicable for the current Schema Object type. | 
| Code | OPENAPI3STANDARDS_L188 | 
| Type | Linting | 
| Rule System | Semantic | 
| Broad Category | Schemas | 
| Products Impacted | API Transformer, Code Generation, Developer Experience Portal | 
| Tags | openapi3openapistandardssemanticlintingcontent schemastringschema | 
Suggested Fixes
- Ensure that the value of typein the Schema Object is not set to a value other thanstring.
- Type names are compared in a case-sensitive manner.
- If you use the contentSchemakeyword, ensure that the data instance you intend to validate can be a string.
- If the type of the instance can vary i.e. it can be an string or some other type, consider removing the typekeyword to allow any types. If you use theoneOf/anyOfconstructs instead, consider moving thecontentSchemato theoneOf/anyOfschema that has the type set asstring.
For More Information
- https://datatracker.ietf.org/doc/html/draft-bhutton-json-schema-validation-00#section-8
- https://datatracker.ietf.org/doc/html/draft-bhutton-json-schema-validation-00#section-8.5
- https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#schema-object
- https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.0.3.md
- https://docs.apimatic.io/rulesets/overview/