-
Notifications
You must be signed in to change notification settings - Fork 87
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
Function Names #186
Comments
Refer here for an exemplar: https://github.com/inaka/elvis/blob/master/src/elvis_style.erl#L151
|
Add a file with improper function names in test_examples, make sure the new function complains appropriately. |
Uses Common Test, not EUnit. |
Ask here, or for more immediate feedback, http://inaka.net/hipchat |
…TE.erl, using new example files added in 4ade99
Currently only covers exported functions
I have some initial work at master...kbaird:Issue#186-FunctionNames. At the moment, it only covers exported functions, whereas I assume we want to try to catch bad names even for private/hidden functions, so that's my next plan. @elbrujohalcon Do you see anything else wrong with the approach or style so far in that branch's additions that you would prefer to be changed before the final PR? |
@kbaird It’s looking great, so far! |
…t hidden functions are still checked
I'm not super-happy about the dpulication between the anonymous functions within exported_functions/1 and function_names/1. I may revisit those.
More work in progress: kbaird/elvis@Issue#186-FunctionNames...kbaird:Issue#186-FunctionNames-AlsoHidden |
Returns anonymous Funs that were previously inline
… is a common-test need for modules that does not apply to function names
We need a rule like the one we have for module names, but for function names (with a regular expression as the parameter and maybe a list of exceptions)
The text was updated successfully, but these errors were encountered: