Skip to main content

valid-custom-type-field-primitive-type

Overview

This rule belongs to the apimatic-post-processing-validation ruleset and states that:

Some types like "File", "Void" and "Dynamic" are not applicable to model fields and, therefore, will be auto-converted to their equivalent valid types.

PropertyValue
EnabledNo
Maximum SeverityWarning
MessageType specified is not applicable to model fields and has been auto-converted to an equivalent valid type.
CodeAPIMATICPOSTPROCESS_V404
TypeValidation
Rule SystemSemantic
Broad CategoryGlobal Types/Models
Products ImpactedCode Generation, Developer Experience Portal, API Transformer
Tagsapimatic postprocessing validation type primitive type scalar type field model property custom type complex model

Suggested Fixes

  • Use only valid and supported primitive types for model fields e.g. "Binary" instead of "File", "Object" instead of "Dynamic".

For More Information