Anypoint Best Practices

general > operations-must-have-identifiers

Guidance / Message

Provide identifiers or display names for the operations.

Examples

valid

/events:
  get:
    displayName: get
    description: Gets a stream of results
    responses:
      200:
        description: Ok!
        body:
          application/json:
            type: string

invalid

/events:
  get: # missing displayName/identifier
    description: Gets a stream of results
    responses:
      200:
        description: Ok!
        body:
          application/json:
            type: string

Applies to Operation

Constraint

Type: Declarative Validation