-
Notifications
You must be signed in to change notification settings - Fork 686
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
A list of examples with proper precedence to help writing unit tests. #833
Comments
Look for the thread(s) where we honed the example regex. You should find some valid and invalid examples. |
See https://regex101.com/r/vkijKf/1/. Not in precedence order, but otherwise a pretty good list.
|
Should |
i'd expect after, which is why usually one would do |
I would also support something like this; I wanted to make the |
Implementing a
SemVer
type is somewhat complex. This is mostly due to some subtle precedence rules.To help with that it would be great to have a list of version strings to be used in unit tests. Ideally there would be...
These test tables should cover various edge cases and are designed to detect flaws in the implementation.
To illustrate what I mean I'll add some of my own tests (from a Swift implementation of SemVer):
The text was updated successfully, but these errors were encountered: