-
-
Notifications
You must be signed in to change notification settings - Fork 226
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
update eslint; types/lint fixes #307
Conversation
26eec07
to
c5367c3
Compare
b903626
to
0200f8d
Compare
6076795
to
50c436c
Compare
@@ -154,7 +154,7 @@ describe('encryption', function () { | |||
it('should throw if passed null public key', function () { | |||
expect(() => | |||
encrypt({ | |||
publicKey: null, | |||
publicKey: null as any, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: We could use // @ts-expect-error
in each of these places rather than casting to any
. It's a bit safer in that we get notified if the type error goes away.
It also prevents the any
type "leaking" onto other lines where the type checking would still be valuable (not applicable here because null
is a literal, but it might apply if this was done to a variable).
9b78df6
to
20948d7
Compare
20948d7
to
b25ed4f
Compare
This comment was marked as resolved.
This comment was marked as resolved.
9d03d87
to
eb00077
Compare
eb00077
to
bab5f82
Compare
|
Mostly looks good! I can approve once the issue with tests being published has been fixed. |
@SocketSecurity ignore shiki@0.14.2 |
eslint
@7.30.0
->8.27.0
@types/bn.js