Vladimír Gorej
Vladimír Gorej
The fix is submitted but the tests are not passing. Can you please provide testfixes for this bugfix ? After that I am happy to make a new release.
That's great, thx ;] On Fri, Mar 7, 2014 at 12:49 PM, sirex [email protected] wrote: > Just want to inform, that I started to work on ini format support. >...
Hi @aharin, It's related to the fact that OpenAPI 3.1.0 resolution is facilitated by [ApiDOM](https://github.com/swagger-api/apidom) which utilizes (currently) full duplication and normalization algorithms. I can imagine this is not warranted...
@Harris-Miller not competent enough in TypeScript to give opinion here.
@vibhuti019 sure, give it a try. Looking forward for a PR!
It's most probably because of the fact that swagger-client now utilizes spec compliant Path Templating implementation. The spec is still ambiguous about various cases like the one that probably affects...
Hm then that's strange. If you have path parameters matching the template (have you changed the `Parameter Object`.`name` field?), it should just resolve. There is a test guarantying this to...
Can you please confirm you can still see the issues in [latest SwaggerUI release](https://github.com/swagger-api/swagger-ui/releases/tag/v5.18.2)?
@falbert-ptc thanks for confirming. Closing this issue. Please reopen if this is not resolved.
It looks like your dependency tree is corrupted or ambiguous. I recommend to run `npm dedupe` or (uninstalling swagger-ui-react and installing it again)