Jeremy Whitlock

That's how it _should_ work. Maybe we're not doing that and this would in fact be a bug. I'll get this fixed ASAP!

I'll get it out today. Sorry, priorities didn't let me get to it sooner.

I have this fixed locally, but I need to upgrade gulp so that TravisCI passes. My plan is to update all dependencies, and gulp, commit and once the build is...

I just went ahead and cut a release. `[email protected]` fixes this issue.

@dillonredding Do you mind verifying this implemented what you were requesting?

From a consistency perspective, what was implemented makes sense. The idea is that when you have a circular reference, we leave it as-is and let whatever tooling is there to...

I get what you mean, and it might be easier than I thought. I'm going to reopen this to avoid it falling through the cracks.

There's two things here and I'll discuss them individually. **Definition Location** The definition location _is_ recorded as the key of the `refs` property. Now...for documents with external/remote references, the everything...

`refDetails` provided to `RefPostProcessor` should have the location. If it doesn't, it's a bug.

Is this referenced from the parent document? If so, you could compute the path based on the knowledge of the parent document. Also, what version of `json-refs` are you using?