James Messinger

Hi @AlexHolly. Thank you for the PR. It looks like that code should probably go inside the `MissingPointerError` class instead (with additional data passed as parameters to the constructor).

Thank you so much for all the detailed information! Sounds like I have a lot of work ahead of me, but I like the direction that JSON Schema and OpenAPI...

@handrews - I've started working on implementing JSON Schema 2019-09, and I'd like to know more details about how `$ref` is supposed to work alongside other keywords. In your comment...

Thanks for the detailed response. It helped me understand the thinking behind the `$ref` behavior, especially how merging/overriding would break expectations of other parts of JSON Schema. I like your...

@philsturgeon - This functionality is implemented (for both Draft 4 and 2019-09) in [JSON Schema Reader](https://github.com/APIDevTools/json-schema-reader), or, rather, in [the internal library](https://github.com/APIDevTools/json-schema) that it uses under the hood. The key...

Unfortunately, there's not currently a way to determine the source of the `$ref` inside a resolver. It only gives you the `$ref` itself. It would be a good idea to...

Yup. That's what I was thinking as well. Thanks for helping out! 🥇 💯

The bundle command replaces _one_ `$ref` to a particular value with the value itself, and then replaces all _other_ `$refs` to that same value with a pointer to the first...

There's nothing in JSON Schema $Ref Parser that would add port 3000 to URLs. You can verify this yourself by checking the URL at [this point in the code](https://github.com/BigstickCarpet/json-schema-ref-parser/blob/master/lib/resolvers/http.js#L147-L154) to...

@andru - Wow, thanks for the thorough explanation! I like your idea of setting _both_ `hostname` and `host`. That's probably the best solution for now, and I'd gladly accept a...