When datatypes in WCF contain nested classes, these classes don't make it to the definitions section of the yaml and swagger editor produces errors.
I've attached some fixes in a diff format that solves this a bit, but the proper solution would loop through the definitions list in a while loop until no further definitions are added anymore.
Hi, is there any improvement in this issue? I'm experiencing the same problem, the only solution is to manually patch the generated yaml adding the missing definitions
When datatypes in WCF contain nested classes, these classes don't make it to the definitions section of the yaml and swagger editor produces errors.
I've attached some fixes in a diff format that solves this a bit, but the proper solution would loop through the definitions list in a while loop until no further definitions are added anymore.
add_more_definitions.txt