[SWAGGER] Make it consistent with reality
- Make the `UserSettings` definition an non-array, this is consistent
with the existing endpoints that uses this definition.
- Resolves #4179
(cherry picked from commit 5926ed1f73
)
This commit is contained in:
parent
6cb63e03e1
commit
dc228b4734
2 changed files with 2 additions and 5 deletions
|
@ -46,5 +46,5 @@ type swaggerResponseUserHeatmapData struct {
|
|||
// swagger:response UserSettings
|
||||
type swaggerResponseUserSettings struct {
|
||||
// in:body
|
||||
Body []api.UserSettings `json:"body"`
|
||||
Body api.UserSettings `json:"body"`
|
||||
}
|
||||
|
|
3
templates/swagger/v1_json.tmpl
generated
3
templates/swagger/v1_json.tmpl
generated
|
@ -25014,11 +25014,8 @@
|
|||
"UserSettings": {
|
||||
"description": "UserSettings",
|
||||
"schema": {
|
||||
"type": "array",
|
||||
"items": {
|
||||
"$ref": "#/definitions/UserSettings"
|
||||
}
|
||||
}
|
||||
},
|
||||
"WatchInfo": {
|
||||
"description": "WatchInfo",
|
||||
|
|
Loading…
Reference in a new issue