Correct externalDocs.description wording in qos-booking.yaml - #118
Merged
hdamker merged 1 commit intoAug 7, 2026
Merged
Annotations
3 warnings and 3 notices
|
Emit annotations:
code/API_definitions/qos-booking.yaml#L699
[S-211] Potentially unused component has been detected. | Suggestion: Remove the component if it is obsolete, or reference it from the API definition.
|
|
Emit annotations:
code/API_definitions/qos-booking.yaml#L696
[S-211] Potentially unused component has been detected. | Suggestion: Remove the component if it is obsolete, or reference it from the API definition.
|
|
Emit annotations:
code/API_definitions/qos-booking-and-assignment.yaml#L1235
[S-211] Potentially unused component has been detected. | Suggestion: Remove the component if it is obsolete, or reference it from the API definition.
|
|
Emit annotations:
code/API_definitions/qos-booking.yaml#L731
[S-313] Schema of type string should specify a format, pattern, enum, or const. | Suggestion: Acceptable if free-form field or implementation-dependent — no fix needed.
|
|
Emit annotations:
code/API_definitions/qos-booking.yaml#L721
[S-313] Schema of type string should specify a format, pattern, enum, or const. | Suggestion: Acceptable if free-form field or implementation-dependent — no fix needed.
|
|
Emit annotations:
code/API_definitions/qos-booking.yaml#L686
[S-313] Schema of type string should specify a format, pattern, enum, or const. | Suggestion: Acceptable if free-form field or implementation-dependent — no fix needed.
|
background
wait
wait-all
cancel
parallel
Loading