-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add a flag & config for skipping path glob patterns #350
Conversation
👷 Deploy request for squawkhq pending review.Visit the deploys page to approve it
|
@@ -27,6 +27,7 @@ squawk-parser = { version = "0.0.0", path = "../parser" } | |||
squawk-linter = { version = "0.0.0", path = "../linter" } | |||
squawk-github = { version = "0.0.0", path = "../github" } | |||
toml = "0.5.9" | |||
glob = "0.3.1" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think eventually it'd be cool to support globs for finding paths
/// | ||
/// --exclude-path='*user_ids.sql' | ||
#[structopt(long = "exclude-path")] | ||
excluded_path: Option<Vec<String>>, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I removed the use_delimiter setting because I think paths can containe ,
. Now users can specify the --exclude-path
flag multiple times instead.
Thank you for the PR @rdaniels6813! |
squawk-cli@0.29.0 has been publish to NPM |
Adding a CLI flag as well as a field in the config file for skipping paths using glob patterns. This is useful for introducing the linter on an already live service which had linter warnings on previous migrations.