Nested ref$ limitation will be addressed as part of this work item https://trello.com/c/hMovZ5jK at least for OpenAPI v3 but potentially for v2 as well.
Thanks for the feedback – be great to get continued input on this. Keep the votes coming!
A must have for financial and regulated industries
270 votesunder review · 11 comments · API Management » Developer portal · Flag idea as inappropriate… · Admin →
+ key rotation
I have similar issue where customers don't want their developers to download the source code on untrusted devices or have access to the source code when they have left the company. We need a way to protect the source code for leaks. In other words when a developer leave the company he should not be able to access the source code on his local machine. The solution proposed by Paul Mooij addresses the access to VSTS/Git but does not prevent a developer to access a copy of the source code after he has left the company.
Thanks for reaching out. We hear you and we are working on it but will be delivering in CY18.