Closed devklick closed 5 months ago
If you're talking about version range like 1.2.x
, I think you should use SemanticVersioning.Range
class instead of SemanticVersioning.Version
and SemanticVersioning.Range
already accepts "1.2"
as >=1.2.0 < 1.3.0--
Yeah range makes more sense in this scenario, thanks.
Hello,
Is it possible to construct a Version/parse a string into a Version without a minor version?
For example, I'm hoping for something like the following:
At the moment, this throws an
ArgumentException
I thought maybe passing
loose = true
would solve the issue but unfortunately not.Going by the npm semver readme, it seems maybe this should actually be treated as
1.2.x
: