Skip to content

Commit

Permalink
Update Chat Swagger Url to the Final File (Azure#14503)
Browse files Browse the repository at this point in the history
* Update swagger url to the final file
  • Loading branch information
LuChen-Microsoft authored and vindicatesociety committed Apr 26, 2021
1 parent 856b689 commit b7a6713
Show file tree
Hide file tree
Showing 3 changed files with 3 additions and 3 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -183,7 +183,7 @@ export const createChatThreadRequest: OperationParameter = {
export const repeatabilityRequestId: OperationParameter = {
parameterPath: ["options", "repeatabilityRequestId"],
mapper: {
serializedName: "repeatability-Request-Id",
serializedName: "repeatability-request-id",
type: {
name: "String"
}
Expand Down
2 changes: 1 addition & 1 deletion sdk/communication/communication-chat/swagger/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ description: Chat Client
generate-metadata: false
license-header: MICROSOFT_MIT_NO_VERSION
output-folder: ../src/generated
input-file: https://int.chatgateway.trafficmanager.net/swagger/2021-03-07/swagger.json
input-file: https://raw.githubusercontent.com/Azure/azure-rest-api-specs/master/specification/communication/data-plane/Microsoft.CommunicationServicesChat/stable/2021-03-07/communicationserviceschat.json
model-date-time-as-string: false
optional-response-headers: true
use-extension:
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -60,7 +60,7 @@ describe("[Mocked] ChatClient", async () => {
assert.equal(request.url, `${baseUri}/chat/threads?api-version=${API_VERSION}`);
assert.equal(request.method, "POST");
assert.deepEqual(JSON.parse(request.body), sendRequest);
assert.isNotEmpty(request.headers.get("repeatability-Request-Id"));
assert.isNotEmpty(request.headers.get("repeatability-request-id"));
});

it("makes successful list threads request", async () => {
Expand Down

0 comments on commit b7a6713

Please sign in to comment.