Split Version Entity into Version and VersionRange #9

Open
gossi opened this Issue Mar 24, 2013 · 1 comment

Projects

None yet

2 participants

@gossi
Collaborator
gossi commented Mar 24, 2013

At the moment, this is all in Version but should be separated.

@stof
stof commented Oct 21, 2013

It should probably be named VersionConstraint rather than VersionRange though, as a requirement constraint is not always a range (for me, a range implies an upper bound and a lower bound). Thus, composer supports OR in constraints now, which makes it even more difficult to consider as a range (you will have a union of ranges)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment