Currently, whenever a comment is made on an API with which I'm associated, I receive an email notification with a subject that is something like "gareth.davies has just added a comment to your API" (similar for replies). Since, as an Org Owner, I'm associated with dozens of APIs it is unclear from the email Subject alone which API has been commented on. Is there any way of including the API name in the Subject line?
small feature requets: it would be great, if the default version in the versin popup would be the either the latest published or - if no published is available - the latest unpublished.
Thanks and best regards,
kepp up the great work
We need LDAP Integration for SwaggerHub. Currently, users have to manage an additional user credentials. With most of the products being LDAP-Integration enabled, we would like to expect the same for SwaggerHub. What plans do you have for this to be available?
My team has started versioning some of our APIs. I noticed that the sort on the versions drop down was not sorted and makes it more difficult to find what you are looking for. It seems to me that by default version ascending would make sense. This is not a big deal with just a few versions, but I can see it become a pain in the future.
I would expect to see
When working on an API in SwaggerHub with multiple integrations, every time I update the API, each integration kicks in (pushing multiple commits to GitHub, updating AWS, etc).
In order to iteratively work on my API in small steps, I need to disable each integration one-by-one, and then re-enable them one-by-one when I get my API where I want it to be.
It would be useful to have a fast (one-click) way to disable and then re-enable all integrations so that I can work on my API without thrashing my integration targets.
An API can support several response codes and projections even in an Idempotent operation. For clients which expect to use the API and mock out the cases, they need to be able to control what case (response) their attempting to exercise. Having the mocking VertServer cycle through the possible response examples doesn't allow the api developer / integrator or tester to have reproducible results (manually or programmatic ally). It would be nice if, when making a request, the client could provide a header describing which response case it would like to exercise. It would also be nice if the virt server baseUrl was not stored as part of the contract and could be turned on or enabled on a request basis so administrators wouldn't have to change the contract just for a client / team to test the mock contract.
I'd like to add another contributor permission and differentiate those users which can edit the contract vs. those who can edit the descriptions. This is important as we'd like to add Tech writers as a contributor, however we want to be careful that they can't accidentally change the contract.
The generation of c# puts descriptions in the <Remarks> tag for the operation on the controller. This is ok but it tends to pollute the code and doesn't preserve the white space of the markdown. We'd like to have swaggerhub generate resource files that we can link into our c# micro-service and use the swashbucke IDocumentFilter to read those files from code resources and provide them in swagger output. This would also allow us to handle localization concerns in the future much more effectively.
Why: because once we generate the code, we push our micro-service through our continuous delivery process and only publish to our gateway from the micro-service host swagger. So the format of those descriptions need to be maintained and presented by the code itself.
Currently when two or more editors are editing an API swagger, they get a notification that both are editing and one will lose their changes. Editors / Commentors won't editor or comment when it happens for fear that they could overwrite some import changes made by the other participants.
Feature: Confluence has a feature where you can see when the other user is editing the same document so you can be sure you're not working on the same changes. It would be great if we could either get a) detection and merge capabilities when saving for multi-editing or b) realtime view of editing by multiple parties.
Should at least prompt if comments are going to be lost. Would like to be able to download / save the comments. Perhaps support for saving these comments to confluence and/or bitbucket.
I'd love it if I could setup an API / Operation to integrate with BitBucket such that every time I save the API it would create a branch in my repo for the API
We have several APIs and in order to integrate these with Azure and BitBucket, I have to provide the integration details on every API version; which gets daunting. I'd like to be able to set this at the API container level or organization level so I don't have to reset them again.
I'd like to be able to use my own domain for the UI and the swagger spec itself.
What I'd like is something similar to what Read the Docs does. Everything is still hosted on their site, it's just accessed using one of my domains.
As an example, I'd like something like swagger.example.com, where example.com is a domain I own, to be the base URL for the swagger UI for my APIs.