Skip to content

Commit

Permalink
Fix support swagger correctness violation (Azure#11709)
Browse files Browse the repository at this point in the history
* updated version, example and schema changes

* fixing examples and updating readme files

* Update support.json by gangan

Removed html tags (kept some <br/> but can remove them as well)
moved all of the links to md style.

* Update support.json

Added CSP and Sev 1 description

* Updates from swagger json review

* Updates from examples review

* prettier check

* updating custom words and running prettier

* fixing path in readme.go.md

* Reverted change from invalid upstream merfe

* Fix swagger correctness violation for integer type format

* Try to change format to int64 since int32 is flagged as breaking change

* Revert "Try to change format to int64 since int32 is flagged as breaking change"

This reverts commit cb602d9.

Co-authored-by: Bhavin Shah <bhshah@microsoft.com>
Co-authored-by: shahbj79 <shahbj79@hotmail.com>
Co-authored-by: Ganga Narayanan <gangan@microsoft.com>
Co-authored-by: Nilay Chheda <nichheda@microsoft.com>
  • Loading branch information
5 people authored and giromm2ms committed Dec 20, 2020
1 parent 40acda2 commit 6c1aa11
Showing 1 changed file with 5 additions and 2 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -294,7 +294,8 @@
"in": "query",
"description": "The number of values to return in the collection. Default is 25 and max is 100.",
"required": false,
"type": "integer"
"type": "integer",
"format": "int32"
},
{
"name": "$filter",
Expand Down Expand Up @@ -616,7 +617,8 @@
"in": "query",
"description": "The number of values to return in the collection. Default is 10 and max is 10.",
"required": false,
"type": "integer"
"type": "integer",
"format": "int32"
},
{
"name": "$filter",
Expand Down Expand Up @@ -1253,6 +1255,7 @@
"slaMinutes": {
"description": "Service Level Agreement in minutes.",
"type": "integer",
"format": "int32",
"readOnly": true
}
}
Expand Down

0 comments on commit 6c1aa11

Please sign in to comment.