-
Notifications
You must be signed in to change notification settings - Fork 111
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
Qulice allows catch parameters not following naming convention #627
Comments
@mkordas doesn't it work already?
Is this configuration wrong? |
@krzyk both names are matching our regex: http://regexr.com/3cki7 |
@mkordas so the |
@mkordas ping |
@krzyk done, thanks for pinging |
@davvd valild bug |
@davvd valid bug |
@davvd this is postponed |
@mkordas thanks for the report, I topped your acc for 15 mins, payment ID |
@davvd this is not postponed |
@krzyk the regular expressions of LocalFinalVariableName, LocalVariableName, MemberName, and ParameterName are working fine and do not require changes
|
@kitsook let's make all the regexes you mentioned to the |
@kitsook thanks! |
Currently Qulice does not complain on the following catch parameter names:
I'd expect violation on both of these names. Only
ex
or 3-12 lowercase latin characters should be allowed.Pattern should be
^(ex|[a-z]{3,12})$
. Moreover, rest of patterns should be unified to follow the convention: replace^id$|^[a-z]{3,12}$
with^(id|[a-z]{3,12})$
in LocalFinalVariableName, LocalVariableName, MemberName, ParameterName.The text was updated successfully, but these errors were encountered: