-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Snake case #500
Snake case #500
Conversation
it probably makes no sense to clean up all variable and method names in one PR because that would lead to a very large patch which would be impossible to review. @shelld3v Does this look good to you so far? Feel free to modify in my repo again. |
Why? I don't understand why you do this, most of variables I created when updating dirsearch are something like camelCased |
It's not something |
I still don't think it's a good idea |
You don't have to go with it. The whole point of PEP8 though is that there are shared guidelines. So, if you were to find a contributor who is used to Python guidelines, they'd likely use snake case just as a Java coder would likely use camel case. Right now, the code base has not fixed style and my conclusion would be to go with what is generally adopted in the language it is written in. But, once again, it's your code base, so I'm only making a suggestion. |
@maurosoria I've resolved the conflicts. |
I actually don't like this PR, but I'm not the owner |
Following on from #446 this PR transforms some camelCased names to snake_case.
This does not close #144 because there are many more occurrences of camelCase which should really be snake_case.