Open ouadi opened 6 years ago
@ouadi There isn't way "to force" to use a specific version of swagger_ui at the moment, plus we have to investigate if that's really just a problem of "swagger-ui" or it happens when we parse the spec....
Will it be possible to suggest a work-around for the time being? With this issue, my very first use of hexo-theme-doc
to document an API is completely blocked.
I highly appreciate you help.
Hey,
Sincere apologies for a delayed response.
Since the issue with swagger-ui
is already fixed and we are using relaxed versioning(^
) for it so you should get the update without any change.
I am also updating the version of swagger-ui
to the latest version.
For swagger-to-html
, I will fix the issue but it might take some time.
Many thanks for your valuable help and involvement. I will wait for the fix.
@All - Any updates on this please ?
Expected Behavior
swagger_ui
andswagger_to_html
should render a Swagger spec that contains circular $ref.Actual Behavior
hexo generate
orhexo server
crash and show the following error:The issue is at the level of
swagger-ui
and is known (see UI crashes when the definitions contain circular references). It has been already fixed.The question is: how to force
hexo-theme-doc
to use the fixed version ofswagger-ui
?Steps to Reproduce the Problem
swagger_ui
tag orswagger_to_html
taghexo generate
orhexo s
Specifications