Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .stoplight/styleguide.json

Large diffs are not rendered by default.

17 changes: 17 additions & 0 deletions cs/v1/CS_v1.0.3.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -233,6 +233,23 @@ paths:
- `CY` (Container yard (incl. rail ramp))
- `SD` (Store Door)
- `CFS` (Container Freight Station)
- schema:
type: string
default: DRY
example: REEFER
in: query
name: cargoType
description: |
This parameter can influence:
* the routing solutions returned
* the feasibility of individual transport legs
* the reported footprint values, when provided

Possible values:
- `DRY` (For DRY cargo)
- `REEFER` (Reefer cargo)

The default value is `DRY` in case this filter parameter is not used.
Comment on lines +236 to +252
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Action required

1. cargotype missing enum + optionality 📎 Requirement gap ≡ Correctness

The new cargoType query parameter is documented without a schema enum for DRY/REEFER and
does not state that provider support for this filter is optional (only a default is described). This
fails the documentation requirements for supported values and optional provider support.
Agent Prompt
## Issue description
The OpenAPI parameter `cargoType` does not enforce/document the allowed values via schema `enum`, and it does not explicitly state that provider support for the filter is optional (as required).

## Issue Context
Compliance requires documentation to enumerate supported values `DRY` and `REEFER`, and to state that provider support is optional; when supported, consumer usage is optional and provider defaults apply when omitted.

## Fix Focus Areas
- cs/v1/CS_v1.0.3.yaml[236-252]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

- schema:
type: integer
format: int32
Expand Down
Loading