Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
clarification needed: hapi-swagger vs hapi-swaggered + hapi-swaggered-ui
See original GitHub issueI have been a (mostly) very satisfied user of this module hapi-swagger. Many thanks to the chef, and to everyone else who has helped me on this forum over the past many months. I am very grateful for it all.
However, I just noticed hapi-swaggered and its companion hapi-swaggered-ui project (I am late to all parties). A recurring theme on this (hapi-swagger) project seems to be that the ui and its components are hard-coded in (hence, recently discovered incompatibles with the newest versions of Joi and handlebars etc.) and it is difficult to upgrade to Swagger 3.0 and, quite understandably, those who know how to do the upgrade are busy with other more important things.
So, my questions are thus:
-
What are the non-obvious differences between
hapi-swaggerandhapi-swaggered+hapi-swaggered-ui? -
Why not merge the two projects and collaborate in order to benefit from the energies of the bigger user pool?
Issue Analytics
- State:
- Created 5 years ago
- Comments:5
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Another point of comparison, this time of the network traffic:
hapi-swagger (this project): 31 requests 2.95 MB hapi-swaggered-ui: 7 requests 1.38 MB
closing this since I’ve made updates to latest swagger ui in 636c2e06e87d9670f9ccabd1f197de39e5a647cc. Both hapi swagger ui libs provide similar features and the underlying core lib is the same
swagger-ui-dist.