So that exclusions can be shared in a multi-person team. Otherwise, you have to trust that everyone excludes the same things (for example all the unmodeled AspNet tables). I picture a json file with a special name that has the exclusions. I know I've considered this before, for example #13. Another case that came up recently is #14. I'd like to be able to exclude that FK globally for all repo contributors.
adamfoneil
commented
3 years ago
So that exclusions can be shared in a multi-person team. Otherwise, you have to trust that everyone excludes the same things (for example all the unmodeled AspNet tables). I picture a json file with a special name that has the exclusions. I know I've considered this before, for example #13. Another case that came up recently is #14. I'd like to be able to exclude that FK globally for all repo contributors.
I'd continue to support private exclude lists.