-
Notifications
You must be signed in to change notification settings - Fork 0
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
re.match expecting a string but getting a list #2
Comments
The help text does specifically say a single file, so may be better to lock the command to just checking a single file rather than attempting to make it work for multiple. Thoughts @Jonxslays? |
Maybe just remove the entire -f option all together. Just use the path argument for everything... |
Good find here @IkBenOlie5 . For now I have pushed a band-aid fix up to the develop branch to restore functionality to the -f flag if you only want to parse a single file. This requires more thought and planning I think. There are some design flaws that need to be ironed out. Note: -f will still only accept a single file for now.
Personally I would like to keep the greedy path argument, and maybe we could just do away with |
This issue is now resolved in the v0.2.1 release. You can update to the latest version with |
in handle_when_file
args.path is an instance of a list not a string. This causes len8 to no longer work...
if i pass multiple files into args.path
the list would be
["file1.py", "file2".py]
.(this is because of #1)
The text was updated successfully, but these errors were encountered: