Closed benfalk closed 7 years ago
Can you add some tests around this? (It should be easy to do, given an invalid uri)
Thanks for the feedback @iainbeeston ! I'll work on these :smile:
@iainbeeston I have made some edits, let me know what you think
Yeah that's looking good. Just another couple of changes. Would also be good to get @RST-J to check this too before we merge
@iainbeeston I've re-formatted the errors around a bit, let me know what you think. Thanks!
I added my feedback - just minor things, in general I like this improvement. I can imagine that errors like this are currently not much fun during development.
Hey @benfalk do you have time to implement the few points of feedback?
@iainbeeston yup, sorry for dropping off on this. Been using my fork and this fell off on my radar. I'll get this updated a little later today.
Hey @benfalk - just want to poke you over this, I'd love to merge your PR
Or let me know if you're happy for me to fix it and merge it myself (I'm happy either way)
I've fixed up the last few things and merged manually in 3f07ef0599c9a0e080840bfd1be04df433b7bbff
Thanks @benfalk
When getting a
404
or500
error it was impossible to know which file was causing the problem with a schema that had many external references. This attaches the uri that failed to the error if it's an OpenURI error, which makes is easy to know what refrenced file was the culprit.