-
Notifications
You must be signed in to change notification settings - Fork 661
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
several ts-nocheck
resolved
#1193
Conversation
Ready to be reviewed. |
from: Note; | ||
to: Note; | ||
from: Note | null; | ||
to: Note | null; |
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.
Just curious about having null
and not undefined
. I really wished there was only one thing for that in TS, not two. Though it seemed to me like null
is discouraged in Typescript.
At the end of the file changes list, e.g. in stavetie_tests.ts, there was also a comment about maybe changing null to undefined.
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.
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.
Yes, that's right.
Can you fix the conflicts please? |
@0xfe fixed, ready to review |
Looks good. Thanks Rodrigo. |
There are only two
ts-nocheck
pending to be resolved:One in textnote_tests.ts @ronyeh could you include in #1163?
Another one in typeguard_tests.ts which I do not know how to resolve.