James Messinger

👍 Definitely on the to-do list

There's already some existing discussion going on about this in [Issue #135](https://github.com/APIDevTools/swagger-parser/issues/135). I think your solution could be acceptable, but I'd like to get some other opinions too

I like @MikeRalphson's approach. We could add an option, like say `dereference.$refRename` that defaults to `false`. Any falsy value = remove the $ref as it does currently. Any string value...

@bcherny - Thanks for providing another example of why this feature would be useful. If somebody would like to submit a PR, I'd be happy to review it. However, I've...

I like that idea @bcherny! What does everyone else think? Would this work for your use-case? /cc @wenerme @maxtuzz @MikeRalphson @philsturgeon @ftheomunhoz

Hi @qm3ster. You're right that the 4-parameter function signature isn't currently documented. I'll add that to my to-do list... or I'm always willing to accept a PR. 😄 Basically, the...

The `schema` parameter can't be a string if `path` is also provided. It looks like [the TypeScript definition](https://github.com/BigstickCarpet/json-schema-ref-parser/blob/master/lib/index.d.ts#L39) is incorrect. The confusion probably arose because [the documentation](https://github.com/BigstickCarpet/json-schema-ref-parser/blob/master/docs/ref-parser.md#dereferenceschema-options-callback) was written before...

The `schema` parameter effectively overrides the `$id` of the schema. It does _not_ mutate the `$id` inside the schema or replace it in the output. The `$id` is just completely...

Not yet, no. But a Pull Request is always welcome! [Here is the file](https://github.com/BigstickCarpet/swagger-parser/blob/master/lib/validators/spec.js) that would need to be edited.

Yes, I plan to implement validation for OpenAPI 3.0 too. PRs are always welcome, of course. 😉