We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It looks like the algorithm can't differentiate a field named description from the attribute description.
I have a model like this:
//... more properties before here date: { type: Date, default: Date.now }, servicesRendered: [{ _id: false, Service: { type: mongoose.Schema.Types.ObjectId, ref: 'Service' }, description: String, quantity: Number, price: Number }], paymentTerms: String, //more properties after...
the property "description" is not the description of the model but a property with type String. When converting it to swagger it generates as follows:
"date": { "type": "string", "format": "date-time" }, "servicesRendered": { "type": "array", "items": { "type": "object", "description": function String() { [native code] }, "properties": { "Service": { "type": "string" }, "description": { "type": "string" }, "quantity": { "type": "number" }, "price": { "type": "number" } }, "required": [] } }, "paymentTerms": { "type": "string" },
As you can see, it generates a description "description": function String() { [native code] }, and if failed to load the Swagger UI.
"description": function String() { [native code] },
The text was updated successfully, but these errors were encountered:
No branches or pull requests
It looks like the algorithm can't differentiate a field named description from the attribute description.
I have a model like this:
the property "description" is not the description of the model but a property with type String.
When converting it to swagger it generates as follows:
As you can see, it generates a description
"description": function String() { [native code] },
and if failed to load the Swagger UI.The text was updated successfully, but these errors were encountered: