Skip to main content

valid-custom-type-field-primitive-type

Overview

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

Some types like "File", "Void" and "Dynamic" are not applicable to model fields and, therefore, should not be used in field definitions.

PropertyValue
EnabledYes
Maximum SeverityError
MessageType specified is not applicable to model fields.
CodeAPIMATICPRE_V511
TypeValidation
Rule SystemSemantic
Broad CategoryGlobal Types/Models
Products ImpactedCode Generation, Developer Experience Portal, API Transformer
Tagspreliminary checks validation apimatic 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