Skip to content
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

detect and remove leading 'v' and pad missing version components #7

Open
burn2delete opened this issue Feb 26, 2014 · 3 comments
Open

Comments

@burn2delete
Copy link

the library should look for a leading 'v' ex. 'v.1.2.3' and remove it (since it's not part of the standard) also pading 0 for missing version parts ex. (1.3 becomes 1.3.0, 2 becomes 2.0 or 2.0.0)

@naneau
Copy link
Owner

naneau commented Feb 26, 2014

That's not a bad idea. I want to have it be more in line with the versions as they are used by Composer. X.Y is not a valid SemVer, but I suppose you are right in saying X.Y.0 was probably meant.

@naneau
Copy link
Owner

naneau commented Jun 17, 2014

The main problem here is being standards compliant. Perhaps there's room for a "soft" interpreter, that fixes mistakes that have a probable fix, next to the current, rather harsh one.

@burn2delete
Copy link
Author

Agreed, an optional flag could switch to a much loser pregmatch.

Matthew Ratzke

On Jun 17, 2014, at 11:07, Maurice Fonk [email protected] wrote:

The main problem here is being standards compliant. Perhaps there's room for a "soft" interpreter, that fixes mistakes that have a probable fix, next to the current, rather harsh one.


Reply to this email directly or view it on GitHub.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants