Contributions
Re: Client codegen errors only for specific targets (csharp, java)
Hi! Thanks for the information. I believe the issue is in the FrameSubscription model: packetType: description: ... type: array items: { enum: ["UDP", "ICMPV6", "PA", "PAS", "PC", "PCS"] } Please try changing the items like such: packetType: description: ... type: array items: type: string enum: ["UDP", "ICMPV6", "PA", "PAS", "PC", "PCS"] While itis legal in JSON Schema to let the type of an attribute (items in this case) be defined by the enum, it is not supported in the specification. So being explicit with the type: string should solve the problem.3.5KViews1like0CommentsRe: What are the exact affected and fixed SwaggerUI versions for CVE-2016-7559 & CVE-2016-7918 (CVSS10)?
Hi, this is the community forum for SwaggerHub, NOT swagger-ui. To help us keep focus on the SwaggerHub project, please sendgeneral OSS questions to our Google Group: https://groups.google.com/forum/#!forum/swagger-swaggersocket Or directly to the security team: security@swagger.io1.9KViews0likes0CommentsRe: Most of "edit codegen options" for Spring Server in SwaggerHub are gone
Hi, this is a bug! Thanks for pointing it out, I expect we'll have it addressed in the next 24 hours. Will report back here when we do. As you saw, this only affects server code generation, and not all of them. But it is indeed broken right now.2.3KViews1like0CommentsRe: Host swagger API documentation on my own server
Hi, I also received your emails directly, so it appears that you're using SwaggerHub to develop thedefinitions. I'm assuming that you now want to host the swagger-ui based on your SwaggerHub-defined definitions. Thesuggested flow would be as follows: * Keep your definition in SwaggerHub as the "source of truth". When you want to make changes, you would do so here. * Use the GitHub sync integration to push the swagger JSON or YAML to your GitHub. This would be your "public facing" UI repository. * Add the swagger-ui-dist package to yourGitHub repository from above * Publish your GitHub repository (perhaps using GH-Pages or SwaggerHub webhooks) on change That allows a good flow, where you can have one source of truth for the definition and control over how and where it's pushed for end-user consumption.34KViews2likes7CommentsRe: workflow statuses
Hi there, good question. There are a couple things in play that could affect the answer. First,and working backwards, marking the API design as `published` is the best way to say "done". Next,there is no "official status field" inside the definition structure, but I have found the info/description field to be the best place to put "in your face" status. You can use Markdown to make bold, or even to embed an image in the description, which could indicate the status in your workflow. Finally, comments and resolution of comments is a good way to indicate state (I know you said in lieu of comments, but just saying). You can use them as sign-off based on different needs. I hope that helps, and please post back any other questions or details of your needs.1.9KViews1like1CommentRe: Apparent resolver errors when referencing a Domain
Got it, I'm looking. BTW a simple version of domains referencing themselves can be seen here: https://app.swaggerhub.com/apis/fehguy/demo-api/1.0.1 I have a feelingsomething else is tripping up the resolver. I'm looking into it...4.4KViews0likes3CommentsRe: Apparent resolver errors when referencing a Domain
Hi Jboyd, Domains withself-references are certainly supported, so there must be something that the editor isn't understanding. Could you please add "swaggerhub-support" as a collaborator to your API and your domain so we can look into it? Thank you! Tony4.4KViews1like5CommentsRe: Prevent go-server from adding Logger
Hi, currently there is not a way to do that--it would be a good option though. You should consider configuring the overwrite on the generator in the integration which lets you remove the logger without worry of it being put back on a generation.1.6KViews1like0CommentsRe: Not able to execute API from SwaggerHub
Hi! SwaggerHub executes requests through a proxy on our server so we can deal with the challenges of CORS, etc. So the request actually does go through our server. That means that if your server is inside your firewall (i.e. unreachable from the internet), you will _not_ be able to call it directly through SwaggerHub. We will be adding a feature to disable the proxy (or use a custom one) but that's not yet available.8.4KViews1like0Comments