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
Swagger-UI version: I think editor.swagger.com is using the latest i.e. 3.25.4
Swagger/OpenAPI version: Swagger 2.0
Content & configuration
This looks like another new problem when having 'entries' as property name. Other properties in the same level of 'entries' properties, fails to load with error "Could not render this component, see the console"
I am confirming this issue where any property named entries causes an error. In my case where I am utilizing hapi-swagger which in turn relies on swagger-ui, I get the error below.
Note: I am not missing a valid version field despite the presented error message. This goes away when I rename "entries" to any other field name.
Activity
shindigira commentedon May 26, 2020
I am confirming this issue where any property named
entriescauses an error. In my case where I am utilizinghapi-swaggerwhich in turn relies onswagger-ui, I get the error below.Note: I am not missing a valid version field despite the presented error message. This goes away when I rename "entries" to any other field name.
fix: remove special handling of non-FormData entries
fix: remove special handling of non-FormData entries
fix: remove special handling of non-FormData entries
tim-lai commentedon May 27, 2020
@aloysiustany @shindigira this will be fixed in the next release, via bec6aeb
fix: remove special handling of non-FormData entries
fix: remove special handling of non-FormData entries (#6036)
fix: remove special handling of non-FormData entries (swagger-api#6036)