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
Currently consuming the project as a NPM dependency is a little bit problematic. You'll have to set up a build to copy /dist somewhere and then overwrite index.html with a custom one. The problem with this is that index.html might have received changes beyond just JavaScript (ie. deps change or something).
To make it easier to consume swagger-ui this way it would be beneficial to push the init bit (ie. $(function () { ...) into a separate file (say init.js) and point at that from index.html. In this case you would effectively avoid the problem I described above as long as the file name remains the same.
Currently consuming the project as a NPM dependency is a little bit problematic. You'll have to set up a build to copy
/dist
somewhere and then overwriteindex.html
with a custom one. The problem with this is thatindex.html
might have received changes beyond just JavaScript (ie. deps change or something).To make it easier to consume
swagger-ui
this way it would be beneficial to push the init bit (ie.$(function () { ...
) into a separate file (sayinit.js
) and point at that fromindex.html
. In this case you would effectively avoid the problem I described above as long as the file name remains the same.Related to apigee-127/swagger-tools#163 .
The text was updated successfully, but these errors were encountered: