We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
parseRange
The below example doesn't throw a type error:
import { parseRange } from "@std/semver"; const range = parseRange("invalid"); console.log(range);
Instead it prints the below range object:
[ [ { operator: "<", major: 0, minor: 0, patch: 0, prerelease: [], build: [] } ] ]
The text was updated successfully, but these errors were encountered:
I've been looking at this and we can update it, but it makes another test case fail. How does this relate to the test case on: https://github.com/denoland/deno_std/blob/083b63f428bc64cd45dcabda9b62c9d600805582/semver/parse_range_test.ts#L354-L365
Sorry, something went wrong.
Yes, that's expected. We'd have to tweak the parseRange() parse ranges of different kinds test to recognize thrown errors.
parseRange() parse ranges of different kinds
I think parseRange('blerg') should throw
parseRange('blerg')
Clarifying my previous message, I meant changing tests is to be expected. I'm in agreement that parseRange("blerg") should throw.
parseRange("blerg")
@std/semver
parseRange()
iuioiua
Successfully merging a pull request may close this issue.
The below example doesn't throw a type error:
Instead it prints the below range object:
The text was updated successfully, but these errors were encountered: