Jeremy Whitlock

The new version of `findRefs` should allow this, which will also apply to `resolveRefs`. Here is an example: ``` js JsonRefs.findRefs({...}, { filter: function (refDetails, path) { return meetsCondition(refDetails)); }...

If I understand, you just need an _"out"_ when parsing to stop processing. Other than that, the current `2.0.0` stuff does what you need. If not, can you tell me...

As for PRs, I'm always open to them.

It makes sense. I'll likely not put any time into this until `2.0.0` is at API parity with `1.x` but PRs are fully appreciated. _(I would suggest not doing this...

If I had to guess, I'd think that moving to ES6 would likely happen after the initial `2.0.0` release. I'm not guaranteeing this but I think it could take some...

This is a cool idea. There are a few things that need to be answered before I knock this out. 1. Are you cool with glob matching? 2. Which option...

@josephzidell With option 3 for JSON output, does it concern you that you'd need to `reduce()` the JSON output to get per-file accumulations of the validation errors/warnings?

The more I think about it, I do like the file-based collection of errors and warnings. If the input is a collection of files, the output should be as a...

Yes it is. But we can keep it open here as well.

The changes related to lint will not be accepted. I get that there is a discrepancy with ESLint settings and your editor but I am not changing the project settings...