Skip to content
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

Closed
elbrujohalcon opened this issue Dec 15, 2014 · 7 comments
Closed

Function Names #186

elbrujohalcon opened this issue Dec 15, 2014 · 7 comments
Assignees
Labels

Comments

@elbrujohalcon
Copy link
Member

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)

@kbaird
Copy link
Collaborator

kbaird commented Sep 24, 2015

Refer here for an exemplar: https://github.com/inaka/elvis/blob/master/src/elvis_style.erl#L151

macro_names only cares about uppercase, has no regex. Look also at ktn_code for functions to use as well.

@kbaird
Copy link
Collaborator

kbaird commented Sep 24, 2015

Add a file with improper function names in test_examples, make sure the new function complains appropriately.

@kbaird
Copy link
Collaborator

kbaird commented Sep 24, 2015

Uses Common Test, not EUnit.

@kbaird
Copy link
Collaborator

kbaird commented Sep 24, 2015

Ask here, or for more immediate feedback, http://inaka.net/hipchat

kbaird pushed a commit to kbaird/elvis that referenced this issue Sep 25, 2015
kbaird pushed a commit to kbaird/elvis that referenced this issue Sep 25, 2015
…TE.erl, using new example files added in 4ade99
kbaird pushed a commit to kbaird/elvis that referenced this issue Sep 25, 2015
kbaird pushed a commit to kbaird/elvis that referenced this issue Sep 25, 2015
kbaird pushed a commit to kbaird/elvis that referenced this issue Sep 25, 2015
@kbaird
Copy link
Collaborator

kbaird commented Sep 25, 2015

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?

@elbrujohalcon
Copy link
Member Author

@kbaird It’s looking great, so far!

kbaird pushed a commit to kbaird/elvis that referenced this issue Sep 26, 2015
kbaird pushed a commit to kbaird/elvis that referenced this issue Sep 26, 2015
I'm not super-happy about the dpulication between the anonymous
functions within exported_functions/1 and function_names/1. I may
revisit those.
@kbaird
Copy link
Collaborator

kbaird commented Sep 26, 2015

kbaird pushed a commit to kbaird/elvis that referenced this issue Sep 26, 2015
kbaird pushed a commit to kbaird/elvis that referenced this issue Sep 26, 2015
Returns anonymous Funs that were previously inline
kbaird pushed a commit to kbaird/elvis that referenced this issue Sep 28, 2015
kbaird pushed a commit to kbaird/elvis that referenced this issue Sep 28, 2015
kbaird pushed a commit to kbaird/elvis that referenced this issue Sep 28, 2015
kbaird pushed a commit to kbaird/elvis that referenced this issue Sep 28, 2015
kbaird pushed a commit to kbaird/elvis that referenced this issue Sep 28, 2015
kbaird pushed a commit to kbaird/elvis that referenced this issue Sep 28, 2015
… is a common-test need for modules that does not apply to function names
@jfacorro jfacorro closed this as completed Oct 2, 2015
ElFantasma added a commit to ElFantasma/elvis that referenced this issue Oct 13, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants