Vladimír Gorej

Updated point **3.)** described in proposed technical design of this implementation: https://github.com/swagger-api/swagger-js/issues/1978#issuecomment-799476860

@jdegre thanks for reporting this. We'll look into it.

@jdegre, I can reproduce, thanks for very good Steps To Reproduce. Yes the problem is probably in `specmap`. The pointer `/components/schemas/B2` is being searched in `a.yaml` file, but should be...

Right, so after spending some time fully understanding the implementation, I've came into conclusion that you uncovered problem that I'm not sure we can fix in current architecture of the...

Right, thanks for providing additional info. Eliminating false positives looks like a way to go. **Additional info:** Behavior changed: Swagger-Editor https://github.com/swagger-api/swagger-editor/compare/v3.6.23...v3.6.24 The behavior change most likely came from SwaggerUI change...

@srl295 thank you for reporting this and for providing a failing test. The problem is in [node-fetch](https://github.com/node-fetch/node-fetch) library that we use when `swagger-client` is run in `node.js` runtime. **Actual url...

Hi, Using lodash over native JS and vice versa is highly debated topic lately. Some of the articles I read lately on the topic includes: - https://dev.to/jrdev_/the-battle-of-the-array-titans-lodash-vs-vanilla-an-experiment-b6g - https://areknawo.com/lodash-and-usefulness-of-utility-libraries/ -...

@jimmywarting would you like to own this issue and implement the proposed changes?

As part of this issue, `pick` has been replaced with object destructuring. @jimmywarting nice job!

We define that very precisely here: https://github.com/swagger-api/swagger-js#runtime. IE is not part of that list. Theoretically your change still might work in IE if IE 11 currently falls within this browserlist:...