[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
This commit is contained in:
		
					parent
					
						
							
								7aa3b41dfe
							
						
					
				
			
			
				commit
				
					
						5926ed1f73
					
				
			
		
					 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
									
									
									
								
							| 
						 | 
				
			
			@ -26540,11 +26540,8 @@
 | 
			
		|||
    "UserSettings": {
 | 
			
		||||
      "description": "UserSettings",
 | 
			
		||||
      "schema": {
 | 
			
		||||
        "type": "array",
 | 
			
		||||
        "items": {
 | 
			
		||||
        "$ref": "#/definitions/UserSettings"
 | 
			
		||||
      }
 | 
			
		||||
      }
 | 
			
		||||
    },
 | 
			
		||||
    "VariableList": {
 | 
			
		||||
      "description": "VariableList",
 | 
			
		||||
| 
						 | 
				
			
			
 | 
			
		|||
		Loading…
	
	Add table
		Add a link
		
	
		Reference in a new issue