ON HOLD: Need to consider how to determine if appropriate shading has already been done. How can we direct the custom rules at the post-shading dependency list?
Count the number of matching lines in a file & raise an issue if it exceeds a specified count. Make this a cross-file rule so that for example we can trigger it to be applicable when the SCM path includes "/widely/shared-components/".
Specifically, widely shared components that pull in more than a few dependencies are a red flag.
ON HOLD: Need to consider how to determine if appropriate shading has already been done. How can we direct the custom rules at the post-shading dependency list?
Count the number of matching lines in a file & raise an issue if it exceeds a specified count. Make this a cross-file rule so that for example we can trigger it to be applicable when the SCM path includes "/widely/shared-components/".
Specifically, widely shared components that pull in more than a few dependencies are a red flag.