We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
atom_naming_convention might be wrongly implemented (the default regex part).
atom_naming_convention
I recently noticed non200_ was a possible atom / function_name, but this is probably undesired.
non200_
atom
function_name
Now, if we fix it as per our initial intention (which was...?), it is a breaking change, so we'd need to bump major.
Have non200_ in your code as an atom, or function name.
The regex should be improved, but also... why would non_200 not be accepted?
non_200
The text was updated successfully, but these errors were encountered:
non_200 should be accepted. Let's improve the regex
Sorry, something went wrong.
Yeah, tentatively I'm leaving this here: ^([a-z][a-z0-9]*(?:_[a-z0-9]+)*)(?:_SUITE)?$.
^([a-z][a-z0-9]*(?:_[a-z0-9]+)*)(?:_SUITE)?$
We force:
[a-z]
[a-z0-9]
_
_SUITE
No branches or pull requests
Bug Description
atom_naming_convention
might be wrongly implemented (the default regex part).I recently noticed
non200_
was a possibleatom
/function_name
, but this is probably undesired.Now, if we fix it as per our initial intention (which was...?), it is a breaking change, so we'd need to bump major.
To Reproduce
Have
non200_
in your code as an atom, or function name.Expected Behavior
The regex should be improved, but also... why would
non_200
not be accepted?The text was updated successfully, but these errors were encountered: