Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
How are external references supposed to be treated?
See original GitHub issueWhen running convertFile over (a local clone of) https://github.com/Azure/azure-rest-api-specs/blob/master/arm-apimanagement/2016-10-10/swagger/apimnetworkstatus.json#L49, I get
Error: Could not resolve reference ./apimanagement.json#/parameters/SubscriptionIdParameter
Ideally (from our perspective 😄) those references would be converted blindly, i.e. without touching the external file, but converting the #/... part assuming that the external file undergoes the same conversion.
I see things like common.resolveExternal if resolve is activated (which throws another Error for me), but also that looks as if it would touch the external file. I’d love to contribute, but wanted to hear your side of the story, maybe there is already something in place I’m unaware of. 🙂
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Should be fixed in v2.5.0
Awesome, thanks!