Last updated

requestBody-replacements-unique

Requires the replacements in the step.requestBody object to be unique.

ArazzoCompatibility
1.0.0✅

Design principles

The list of locations and values to set within a payload must not have duplicates that might result in content override.

Configuration

OptionTypeDescription
severitystringPossible values: off, warn, error. Default off.

An example configuration:

rules:
  requestBody-replacements-unique: error

Examples

Given the following configuration:

rules:
  requestBody-replacements-unique: error

Example of a correct replacements list:

workflows:
  - workflowId: events-crud
    steps:
      - stepId: create-event
        operationPath: $sourceDescriptions.museum-api#/paths/~1special-events/post
        requestBody:
          payload:
            name: 'Mermaid Treasure Identification and Analysis'
            description: 'Identify and analyze mermaid treasures'
          replacements:
            - target: name
              value: 'new name'
            - target: description
              value: 'another description'

Resources

 
Next page