stuften-sfg
Occasional Contributor
Joined 3 years ago
User Profile
User Widgets
Contributions
Re: $ref (erencing) a valid OAS3 domain file not working
chichepo , you haven't missed anything. This is exactly as I've configured it in my cloud account and as with mine, when I click on the link to the API file you've published and expand the policy renewal quotation process operation it hangs and times out throws timeouts. If it's working for you perfectly then perhaps there's an issue with my networks config? I'l see what SmartBear come back with. Thanks for testing out in your account. Much appreciated!1KViews0likes1CommentRe: Standardisation errors prevent me from publishing in Teams Licence (not enterprise)
Hi chichepo , The SmartBear support team have confirmed this is indeed an issue with the editor and they are working on a solution. Thankyou for offering your advice and help. Much appreciated. I'll update this issue with the resolution once SmartBear support get back to me. 😉693Views1like0Comments$ref (erencing) a valid OAS3 domain file not working
I have a Domain defined in OAS3 of 472 code lists containing 14,456 code values(enums). I'm trying to reference this from my API spec which is validating correctly except for this one $ref defined in the following format as recommended at the following support page... https://support.smartbear.com/swaggerhub/docs/domains/referencing-domain.html components: schemas: transactionTypeCode: $ref: 'https://api.swaggerhub.com/domains/OWNER/DOMAIN/VERSION#/components/TYPE/COMPONENT_NAME' When I enter ... https://app.swaggerhub.com/domains/OWNER/DOMAIN/VERSION#/components/TYPE/COMPONENT_NAME into the browser it correctly jumps into the domain to the component defined . I thought maybe the size of the domain may be an issue since swagger is slow at validating so I pulled out just one schema component into its own domain, referenced just that one and still have the same error when validating the referencing API. Any help most appreciated!1.2KViews0likes5CommentsRe: Standardisation errors prevent me from publishing in Teams Licence (not enterprise)
Thanks chichepo . Using OAS 3 and v3.0.0. I used Oxygen XML editor to craft the inital API Spec in JSON then loaded into the Swagger editor. Schema components, info tags all validate cleanly in the editor and in Oxygen however when returning to home screen where i can see all my APIs in my project it shows the {error} label and does not allow me to inspect the errors. I started with a Trial version and played around with the standardisation before purchasing the Teams licence. I'm wondering if its carried forward some of those settings into my teams licence.🙄 I just created a new API using the SImple API template and its showing the same error! So I think its definitely an issue with the editor.719Views0likes2CommentsStandardisation errors prevent me from publishing in Teams Licence (not enterprise)
I recently acquired a Teams licence (not an Enterprise Licence). My API is marked as VALID when I'm editing and saving it however its shows a Standardisation error on the main API list view saying it can be saved but not published. Since its a Teams licence there is no way to turn off the standardisation rules and no errors are showing when I'm editing. Any help most appreciated!760Views0likes4CommentsSwaggerHub hanging when I sign in
I just signed up for a Free Trial, completed the registration, went to sign in then login seems to hang. Issue occurs in both Chrome and Edge browsers 🙄 Tried signing in multiple times in both browsers. No internet connectivity or firewall issues. Any help or advice most appreciated! Google Chrome Version 109.0.5414.74 (Official Build) (64-bit) Microsoft Edge Version 109.0.1518.55 (Official build) (64-bit) Windows 10 Pro Version 10.0.19044 Build 19044577Views0likes3Comments