feature/question: sampling a path #362
Description
we have a use case where we're compiling a large number of static pages and as we scale the number of pages we're scaling the amount of time percy-agent takes to process the screenshots.
we'd love a way to "sample" these pages somehow but only reviewing X number of them, as we only get marginal benefit to having percy process each and every one of them (because they share the same template).
one approach is for us to pre-process our files and pass the sample logic via the glob commands but another would be to add an option to the CLI for this that would hook up to the existing path traversal that the agent already does.
percy snapshot buildDir --sample-paths blogs/** ---sample-depth 10
is this of interest? is there a different or better way we should be thinking about this? i'm curious to hear the percy team's take and especially if they've ever had other customers encounter this.