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
There are some options on different languages that are string-type but the default values are boolean-type ( "true"/"false" ).
I think since there are no limitations on using the boolean type, why not change these options to corresponding types to maintain consistency.
{
"packageName": {
"opt": "packageName",
"description": "Go package name (convention: lowercase).",
"type": "string",
"default": "swagger"
},
"hideGenerationTimestamp": {
"opt": "hideGenerationTimestamp",
"description": "Hides the generation timestamp when files are generated.",
"type": "string",
"default": "true"
},
"packageVersion": {
"opt": "packageVersion",
"description": "Go package version.",
"type": "string",
"default": "1.0.0"
},
"withXml": {
"opt": "withXml",
"description": "whether to include support for application/xml content type and include XML annotations in the model (works with libraries that provide support for JSON and XML)",
"type": "boolean",
"default": "false"
}
}
The hideGenerationTimestamp option is a String with a boolean-type value by default ( "true" ), but we also have the option withXml that is boolean type with a default value of "false".
The text was updated successfully, but these errors were encountered:
There are some options on different languages that are string-type but the default values are boolean-type ( "true"/"false" ).
I think since there are no limitations on using the boolean type, why not change these options to corresponding types to maintain consistency.
Options for
Go
language for aV3
Client, using the online generator ( https://generator3.swagger.io/api/options?language=go&version=V3 ):The
hideGenerationTimestamp
option is a String with a boolean-type value by default ( "true" ), but we also have the optionwithXml
that is boolean type with a default value of "false".The text was updated successfully, but these errors were encountered: