I recently suggested using swashbuckle to integrate swagger into our web apis in order to expose the API functionality internally to our engineers. for our purposes, swagger does not make sense in production, since apis are back-end ..... being a corporate environment, the number of APIs is large, and I can anticipate two main problems:
Build size is about 2.6 MB. Suppose that hundreds of avitas with integrated swahbuckle suddenly increased the size of all our applications by 4.5 times. Unreasonable blow. Looking at swashbuckle.core, I suspect that the bulk of this size is bundled with swagger-ui. Is it possible to separate swagger-ui from swashbuckle and instead allow swagger-ui to be added via a separate nuget package.
The nested swagger-ui in swashbuckle has all the api having their own instance of swagger-ui. Any setting made for swagger-ui does not affect other projects, unless they make changes to each api project, increasing effort and reducing the chances of being supported. We host swagger-ui centrally and configure it so that developers can implement their swagger implementation locally (localhost), so this will have a big impact on swashbuckle integrating swagge-ui, and it would be much better to be able to pull swagger-ui through a separate nuget package .
Is there anything in connection with the consideration of the foregoing or is this our best chance to simply unlock and move forward due to the need to maintain it?