Contributions
Re: Apparent resolver errors when referencing a Domain
Oh, I believe it generally worksbecause 1) the UI shows things correctly as long asI hide the errors, and 2) the workaround works. I've seen this a couple times before and just shrugged it off, but with half a dozen errors showing Ifigured it was time to get y'all involved. Thanks for the quick investigation!4.3KViews0likes2Comments- 4.4KViews0likes4Comments
Apparent resolver errors when referencing a Domain
I have an API that contains a reference to a definition in a domain that itself contains references to other definitions in that same domain. E.g.: schema: type: object required: - self - parent foo: bar: $ref: 'https://api.swaggerhub.com/domains/myTeam/Bar/1.0.0-alpha#/definitions/Bar' ... The Bar definition in the Bar domain refers to several otherdefinitions in the Bar domain, and the Bar domain validates. Now, for some reason, when I first load the API definition, the UI complains about some of the references in the Bar definition and marks my API definition as invalid. There's a workaround, though: if I just cut and repaste the $ref line above, those errors go away and the API definition validates. But if I reload the page, there the errors are again. We use SH to communicate w/ outside partners, and even if I could explain the workaround to them, not all of them can edit the definitions. So all they see is this mass of errors when they load the page, which is totally unacceptable. Can you please tell me how to fix or avoid this? The API in question is private, so I don't feel like sharing the link here, but for staff users, my SH username is 'jboyd'. Thanks!Solved4.4KViews0likes6Comments