Evgeny

In branch [cycles](https://github.com/epoberezkin/fast-deep-equal/commits/cycles)

Yes, working on a fix here too… It’s a tricky one, at the time it was implemented the spec didn’t settle yet, but should be ok soon.

Just to add, if mocha tests are pure JS, istanbul shows coverage using available source maps: ``` "test-spec": "mocha spec/{**/,}*.spec.js -R dot" ``` So maybe the problem is to make...

We don't just check meta - more about checking guidelines. E.g., branches are protected, PRs are approved before they are merged, commits are connected to github users, etc.

I think if the team is bigger than 20 people it becomes useful... We have 100 different repos updated every week, 200 every month.

That's why it's BETA :) Select indeed compiles cases as separate schemas without resolving the IDs in them against the current base. Happy with PR marking it as a limitation...

It’s relative JSON pointer spec - “0” means the current level in the data (I.e. 0 levels up). “1” would mean one level up etc.

What’s the use case I wonder...

I am quite excited to learn that ajv (and JavaScript) have such a long and illustrious future to come, and AI apparently didn’t take over, and people still write code,...

I don't understand why you need to validate one deep property from another. It's possible to allow root-based absolute and relative JSON pointers, but that would mean full rewrite of...