-
Notifications
You must be signed in to change notification settings - Fork 56
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
Extend naming conventions with things to avoid #151
Comments
For semantics purposes, a Have you considered negative lookaheads, like > {ok,RE} = re:compile("^(?!do_).*$").
{ok,{re_pattern,0,0,0,
<<69,82,67,80,87,0,0,0,16,0,0,0,1,128,0,0,255,255,255,
255,255,255,...>>}}
> re:run("ado_", RE).
{match,[{0,4}]}
> re:run("do_", RE).
nomatch |
HA! I didn't know about negative lookaheads. |
It could even be |
Could you help me with the regexes? What do we want to add to the forbidden regexes? |
@bormilan the default should be |
Oh, I understand now; the goal is to allow users to specify their |
... and make it explicit in the doc., as @elbrujohalcon states, that whatever is accepted in |
Currently, our naming convention rules only allow for a single regex that identifies what is permitted/valid.
It would be nice to add an additional forbidden regex to identify things that are not valid, like function names starting with
do_
.Ref: WhatsApp/erlfmt#91
The text was updated successfully, but these errors were encountered: