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.
Description
This branch resolves a number of PEP8 violations, and includes some refactoring to use industry best practices and new coding conventions.
Motivation and Context
The following changes are required so that the application is left in a well documented and maintainable state so that future development can commence.
I intent to resolve some of the TODO comments within the solution, refactor the extractor module to provide a cinex/termex implementation which can be piped, and finally implement yara rule based keyword searching. However, want to do so from a clean codebase.
How Has This Been Tested?
Functionally, there has been no breaking changes. That being said I have tested the application by performing all possible workflows of the application; verbose, with-tor, without-tor, crawl, pause, depth, for each extract method, etc.
Please find attached the result sets of the following test cases:
Screenshots (if appropriate):
Types of changes