Skip to main content

non-empty-non-null-example-id

Overview

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

All examples provided for a component must be assigned unique, non-empty and non-null ids.

PropertyValue
EnabledYes
Maximum SeverityWarning
MessageOne or more examples specified against a component were assigned ids that were empty or null. All such ids have been assigned auto-generated values.
CodeAPIMATICPOSTPROCESS_V505
TypeValidation
Rule SystemSemantic
Broad CategoryExamples
Products ImpactedCode Generation, Developer Experience Portal, API Transformer
Tagsapimatic postprocessing validation id example

Suggested Fixes

  • Make sure that all examples have a unique non-empty and non-null id assigned to it.
  • Remove example entries that have empty/null id assigned to them.