This message was deleted.

Thanks for the feedback Brian. You’re not the first who raised exactly this concern so I think we probably just need to prioritise the work to enable $ref support. I’m going to make sure we prioritise discussing this as a team next time we’re doing roadmap work. Out of interest - do you think Swaggerhub has got the design right in this respect, or are there things you wished it did differently?

@Tom as we discussed on the call. SwaggerHub is a tool we mainly use for API review and not design. Our current API workflow is: • Development: Visual Studio Code using $ref for local files. ◦ We use multiple swagger editor plug-ins ◦ Run scipts to set versions in the related files — SwaggerHub needs you to touch each file — which is painful. Thus the scripts and API calls to SwaggerHub. ◦ Bitbucket Repo • Review: SwaggerHub • Testing: Postman • Publishing: Planning Readme.com documentation • API Gateway: Customized WSO2

Thanks for sharing this @Brian Bezanson. Sounds like you’ve had to put a lot of work into your own tooling!