Skip to content

Commit 6126c5d

Browse files
raych1aviyerMSFT
authored andcommitted
Update Semantic-and-Model-Violations-Reference.md (Azure#22942)
add example for LRO_RESPONSE_HEADER fix.
1 parent 1eb0373 commit 6126c5d

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

documentation/Semantic-and-Model-Violations-Reference.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -892,7 +892,7 @@ This document lists the set of automated rules that can be validated against swa
892892

893893
**Description**: Long running operation must return location header or azure-AsyncOperation header in response when this operation is annotated with x-ms-long-running-operation:true.
894894

895-
**How to fix the violation**: Adding one of these headers to the response in example or in traffic payload.
895+
**How to fix the violation**: Adding one of these headers to the response in example or in traffic payload. Refer to this [example](https://github.com/Azure/azure-rest-api-specs/blob/5e638554b6/specification/appplatform/resource-manager/Microsoft.AppPlatform/stable/2020-07-01/examples/Apps_Update.json#L64) for the fix.
896896

897897
### <a name="MISSING_RESOURCE_ID" />MISSING_RESOURCE_ID
898898

@@ -916,4 +916,4 @@ This document lists the set of automated rules that can be validated against swa
916916

917917
**Description**: {header} is declared in response schema in swagger but it's not provided in response in example or in traffic payload.
918918

919-
**How to fix the violation**: Adding this {header} to the response in example or in traffic payload.
919+
**How to fix the violation**: Adding this {header} to the response in example or in traffic payload.

0 commit comments

Comments
 (0)