Scott Mikula

This is on our radar; I just need a bit of time to work through the implications of the upgrade. Should be coming in the next couple months.

Just what I mentioned above; I skipped the `nullOn` and `definedOn` APIs and suspect we won't really need them. I definitely will get the docs updated, but don't want to...

This is something of a pet project for me, so I'm not sure when it might get merged. (Though I do have most of it implemented.) Regardless, you can still...

I'm really interested in a feature like this, too. I think this would be the answer to the question I just posted [here](https://github.com/apollographql/apollo-client/discussions/9161).

My thought with this was to make it a fence.json setting rather than a top level option. Then different subdirectories can apply their own policies.

@nickshevr: One way to get more detail is to look at the raw diff.json file — it will show all the details (albeit in a less readable format). Typically these...

@nickshevr, sure, that makes sense. I'll merge the PR. (Edit: or I will once I get the build to pass...just moved to Github Actions and still figuring it out.)

Currently `good-fences` acts as a whitelist, so you would disallow react by not including it in the `dependencies` array. It seems like you want something more like a blacklist, where...

@menagerie198 Those are both good suggestions. I personally like that Limelight works in preview mode, but that would be a good thing to add a setting for. With regards to...

As envisioned, `good-fences` is meant to be a standalone tool that can run in parallel with other linters or code hygeine tools. Is there a reason you couldn't add it...