Hello My company is using SwaggerHub On-Premise and APIGee as API gateway. We implemented some "Standardization" rules to validate the OpenAPI file syntax within the YAML IDE. Then we run a separated API provided by Google, to validate the OpenAPI file and services logic (here) It would be great to have this validator simply imbedded as an option of the SwaggerHub IDE. By the way, we had cerate a webhook to run it as an integration. Thank you
... View more
See more ideas labeled with:
Could you please consider proxying any authenticated calls from the Confluence page to the SwaggerHub API back through the domain that you presumably serve the widget content from (https://confluence-plugin.swaggerhub.com)? I'm not sure what constraints exist with the Confluence plugin model, but hopefully this would allow you to manage all sensitive state (ApiKey storage) externally in a location we already trust, and form the appropriate authenticated requests to the SwaggerHub API from there. As things stand right now, the SwaggerHub API requests are observable using browser dev tools as the Confluence page renders. These requests include the chosen SwaggerHub ApiKey in the authorization header. This is a security concern for us as we have external parties and partners who we grant visibility to areas of our Confluence tenant so they can view documentation which includes api specifications. Once the ApiKey is compromised, the holder has far more than the readonly-access to specific API specifications that we intended. There are probably other ways to address this, but the proxy approach seemed the most pragmatic to me. We've worked around this issue in the past with other Confluence swagger plugins by only using exported specifications that are attached to the page. However, you are in a good position to allow the convenient referencing of the api specifications in their natural home in SwaggerHub, while keeping the communication paths secure.
... View more
See more ideas labeled with:
Would be useful to allow just the base url to a SwaggerHub API to be specified in the widget configuration. For example: https://api.swaggerhub.com/apis/acme/products Rather than: https://api.swaggerhub.com/apis/acme/products/1.1.0 When the Confluence page is later browsed (and assuming the url is to SwaggerHub), then the default API version should be automatically resolved. This would allow the current state of the API to be reflected in Confluence without requiring new edits every time a new version is published in SwaggerHub. An extension to this would be to allow the users to choose from the different published versions when browsing the page. This should be an opt-in feature on the widget configuration.
... View more
See more ideas labeled with:
The User Management and Registry AIs are very useful - but I'm missing any way of viewing or manipulating team membership. For a specific use case - my organisation is shared among a number of teams that don't have much to do with each other. I want to be able to do things like report on all users in a team, the type of license currently assigned to them, and when they last logged in. The user management API allows me to do most of that, but I can only get the results for the entire organisation - I can't limit it to just the users I'm responsible for. So, the two main things that would be useful: The existing operation for listing organisation members needs a "filter by team" parameter. Some new operations are needed for listing (and optionally, modifying) the members of a team. It would also be nice if "last active time" was one of the sort options for the API.
... View more
Hi! I`ve found something interesting. I cant make Markdown list option in the properties description when i`m using only Cyrillic symbols. To do this i have to take first symbol from Latin alphabet. For example, here is the description with first Latin char: As we see, it`s Ok. But, if i insert Cyrillic char as a first symbol, the list is being destroyed:
... View more
It seems like the diffing tools used for APIs are not available for domains. Diffing domains would make things much easier for our development team. Thanks!
... View more
See more ideas labeled with:
Currently, the developers have a pipeline that acts like a user and uploads generated templates to SwaggerHub. It would be nice if this was an official API route so we are not burdened by UI changes that might break our process. Part of the purpose is so we can validate in our staging SwaggerHub that our end to end flows are working properly. We also trigger a maintenance restart as part of this process for the templates to appear in the UI. Please let me know if you need more detail.
... View more
Each organization should have a wiki page - or at least a stored/clickable URL to enterprise wiki/confluence - so that viewers/developers can get to general doc page of info about the org, dev policies, services standards, etc, whatever. The link would be visible (if set) on the main org API listing page, under the org name. Also in the API editing page in the pulldown section (which lists owner/created by/created date)
... View more
0
Kudos
Status:
Implemented
Submitted on
10-30-2020
01:59 AM
Submitted by
timvanhees
on
10-30-2020
01:59 AM
Please extend the search functionality so searches on API paths can be performed. Ideally with autocompletion so it will be easier to explore the existing API paths of an organisation.
... View more
Owners should have a centralized overview of comments that have not been resolved.
... View more
See more ideas labeled with:
When creating a new version of an API, all comments of the previous version are "lost": they stay in the previous version and become much less visible to the collaborator.
... View more
See more ideas labeled with:
Status:
New Idea
Submitted on
10-14-2020
03:48 AM
Submitted by
oleg_borovyk
on
10-14-2020
03:48 AM
With multiple users invited that means that the admin/owner needs to log in every day to check if someone has accepted the invitation and the appropriate team should be updated. Especially tricky with users/consumers from other companies.
... View more
It would be very useful Models could be given tags so that the documentation could group them the same way that the endpoints are grouped. Then in model generation, instead of all of the models in the model folder, they could be split up into sub folders in the model folder. Not sure if this is swaggerhub Idea, or more for the swagger-generation/swagger-editor repositories, but this is something I would like swaggerhub to do.
... View more
See more ideas labeled with:
Currently we can push to a branch in github the swagger file only. It would be great if we could also have the ability to create a branch and submit a PR at the same time. This would allow my developers to review and feedback. Having the PR status with the swaggerhub UI would be good too
... View more
See more ideas labeled with:
0
Kudos
[Please redirect to right 'location' if this is not the correct one = thanx in advance]
When I download the client SDK for integrating with the API. However all the class names are named with prefix as 'Swag'. If I have to integrate with multiple APIs, I would like the API name to be reflected.
Example CufxClient instead of SwagClient or CufxSwagClient instead of SwagClient.
... View more
See more ideas labeled with:
We can compare two versions of an API, but there is no possibility to produce a report containing the discrepancies between two versions.
Compare popup options
Suggestion : offer a new option that allow producing a report containing the discrepancies.
... View more
See more ideas labeled with:
We have a marvelous tools to help us comparing the modifications between two api versions.
But, currently, the comparaison popup can not be resized. At the end, the usage of this functionality is very restricted.
Unable to resized this popup
My suggestion is to allow the possibility to resize the comparaison popup.
... View more
See more ideas labeled with:
0
Kudos
It s possible to extend the fixed fields in a schema. The specification indicate that we just need to prefix the extra fields with "x-". It s a good point if we want to specified spécific informations - per example the data source of a field.
But, in the produced documentations, at the end, we never see this extra fields.
My suggestion is, optionnaly, we can add/display this extra fields in the final documentation.
Currently, this is what we have :
Example - No extra field displayed
We can expect that we can see the extra field x-dataSource in the documentation.
... View more
See more ideas labeled with:
Hi ,
Please add Add in SwaggerHub to generate springboot code from api and also provide documentation in your help.
Just gone through the spring codegen tool on SwaggerHub and the code genrated project structure is not as per the standard abbreviations and nomencleture we following for RestFul APi project.
With Warm Regards
Om Prakash
... View more
0
Kudos
It would be good to have a feature which can sync java code and API definition both in the Gitlab repository.
Currently, we can choose one out of YAML/JSON resolved or server stub options .
... View more