You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When defining the spec for an integer enum the resulting swagger will parse the enum values as strings, even if the type is integer or number.
To Reproduce
/**
* GET /api/v1
* @summary This is the summary of the endpoint
* @param {integer} state.query.required - name param description - enum:1,2,3
* @return {string} 200 - success response
*/
Creates:
type: integer
enum:
- '1'
- '2'
- '3'
- '4'
Expected behavior
Either give an error, or create the following correct swagger:
type: integer
enum:
- 1
- 2
- 3
- 4
Desktop:
Version 1.8.0
The text was updated successfully, but these errors were encountered:
Describe the bug
When defining the spec for an integer enum the resulting swagger will parse the enum values as strings, even if the type is integer or number.
To Reproduce
Creates:
Expected behavior
Either give an error, or create the following correct swagger:
Desktop:
The text was updated successfully, but these errors were encountered: