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
throw Object.assign(new Error('Not Found'), { code: 'NOT_FOUND' })
currently creates a complaint, but shouldn't because the type of this exception is Error & { code: string }, which is a subtype of Error.
Error & { code: string }
Error
The text was updated successfully, but these errors were encountered:
Note for self: the bug is most likely in the implementation of couldBeType, as Object.assign has this definition:
couldBeType
Object.assign
assign<T, U>(target: T, source: U): T & U;
Sorry, something went wrong.
test(error): Add test for issue #86.
6b26cc5
This should be fixed in 4.17.1.
No branches or pull requests
currently creates a complaint, but shouldn't because the type of this exception is
Error & { code: string }
, which is a subtype ofError
.The text was updated successfully, but these errors were encountered: