Arg for filtering out undesirable content --regexignore #57
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…hes a provided regex pattern example usage: --regexignore "(Page not found|<title>error)"
nseratt
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello @tomnomnom
Hope this can be implemented. I've run into instances where a page will give you a 200 on every request, only to be greeted by an html page saying that it is not found , or that an error occurred.
Feel free to modify as needed. Wasn't sure if -x or --regexignore were the best arg names for it.
Thank you
Description:
Filter out matches where the content body matches a provided regex pattern.
example usage: --regexignore "(Page not found|<title>error)"