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
About extensions, I agree with you that this can be added in the Source tab, especially since the Swagger extensions takes in custom values and could be literally anything.
One suggestion is to enable a key-value pair field exposed in the UI, which can capture the extension name and the extension value.
It also would be useful if we can define the Swagger extensions which are supported for a specific Swagger file. For example, we can mention somewhere in the settings that "PetStore Swagger" should have "x-example" at the Operation/Method level. And when the Swagger code is generated, the x-example value pops up as a field to be filled in (in UI as well Source code). This will ensure that the person documenting the Swagger using the UI/Source tab ensures that the x-example tag is documented and not missed out.
Some basic support for extensions can certainly be added prior to really thinking through how best to support extensions in a more meaningful way. One suggestion for the latter is to support the SEMOASA format: #186
The text was updated successfully, but these errors were encountered:
Comment from: #458 (comment)
Some basic support for extensions can certainly be added prior to really thinking through how best to support extensions in a more meaningful way. One suggestion for the latter is to support the SEMOASA format: #186
The text was updated successfully, but these errors were encountered: