-
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
Breaking: update atom naming convention's default regex #356
Breaking: update atom naming convention's default regex #356
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's add some more atoms to the test to verify our regex even further.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, @bormilan … I think we still need another iteration on this.
It'd be interesting to understand if this is interface-breaking, and signal that as a major in the release, in case it is, because we're changing an existing rule. |
I'll merge this as soon as CI is ✅ … @paulo-ferraz-oliveira I do believe that this deserves a major jump. So… 4.0.0 is coming!!! |
To be clear: I would not release 4.0.0 yet… I would pick a few more tickets to tackle before it goes out. I'll make a milestone and associate a few issues with it. |
There you go, folks: https://github.com/inaka/elvis_core/milestone/7 |
No description provided.