Chrome gets very confused by the sourceMappingURL from swagger-client.js. Use
gulp-sourcemaps to generate our own sourcemap which it is happier with (and
means that the other bits of swagger-ui.js are also correctly sourcemapped).
(and modifying and looking again at those specs iteratively)
new gulp targets:
dev-dist: [lint, copy] (this runs the same code in dist, but without doing a clean first)
dev: [default, serve] (the task to run if you're iteratively making changes and don't want/need the dist directory to be regenerated every time)
* Uses npm to download latest swagger-js (for now. When swagger-js is
released we will replace git address with actual swagger-ui)
* Uses `postinstall` to generate `browser` folder of swagger-ui. This
can go when swagger-ui is published.
By passing parent view as an option to child views, child views can
access parent views and eventually can access model of MainView
There is alos a new domEl option available for SwaggerUI constructor.
User can send domEl instead of dom_id to specifiy which element they
want to render to
