Originally created by @joshuadgoldstein on GitHub (Nov 13, 2013).
It might be nice to include a regular expression which matches your versioning scheme as a sort of "example implementation".
Originally created by @joshuadgoldstein on GitHub (Nov 13, 2013).
It might be nice to include a regular expression which matches your versioning scheme as a sort of "example implementation".
Do you think #205 relates to this, where we're discussing showing how version ranges/operators can be expressed?
@jeffhandley commented on GitHub (Jul 9, 2014):
Do you think #205 relates to this, where we're discussing showing how version ranges/operators can be expressed?
Oh, oh, oh... Now I understand what this issue means! I thought it was saying we should show how regular expressions can be used to match versions. But it actually means showing a regular expression that documents the format of SemVer versions.
@jeffhandley commented on GitHub (Jul 9, 2014):
Oh, oh, oh... Now I understand what this issue means! I thought it was saying we should show how regular expressions can be used to match versions. But it actually means showing a regular expression that documents the format of SemVer versions.
@joshuadgoldstein, see PR #460. This issue was addressed in other threads and and PR is pending to resolve the issue. Unless you have questions or intend to issue an additional PR, please close this issue at your earliest possible convenience. Thank you.
@jwdonahue commented on GitHub (Oct 8, 2018):
@joshuadgoldstein, see PR #460. This issue was addressed in other threads and and PR is pending to resolve the issue. Unless you have questions or intend to issue an additional PR, please close this issue at your earliest possible convenience. Thank you.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @joshuadgoldstein on GitHub (Nov 13, 2013).
It might be nice to include a regular expression which matches your versioning scheme as a sort of "example implementation".
@Oxymoron290 commented on GitHub (Nov 16, 2013):
https://github.com/mojombo/semver/issues/149
@timfriske commented on GitHub (May 20, 2014):
#199
@FichteFoll commented on GitHub (May 20, 2014):
@timfriske, you should have linked the issues in opposite direction since this one here is way older.
@jeffhandley commented on GitHub (Jul 9, 2014):
Do you think #205 relates to this, where we're discussing showing how version ranges/operators can be expressed?
@FichteFoll commented on GitHub (Jul 9, 2014):
I do not think these are related at all.
@jeffhandley commented on GitHub (Jul 9, 2014):
Oh, oh, oh... Now I understand what this issue means! I thought it was saying we should show how regular expressions can be used to match versions. But it actually means showing a regular expression that documents the format of SemVer versions.
@jwdonahue commented on GitHub (Oct 8, 2018):
@joshuadgoldstein, see PR #460. This issue was addressed in other threads and and PR is pending to resolve the issue. Unless you have questions or intend to issue an additional PR, please close this issue at your earliest possible convenience. Thank you.
@steveklabnik commented on GitHub (Feb 11, 2019):
Yes, closing this in favor of the duplicate issue/PR. Thank you!