Replies: 2 comments 1 reply
-
|
Hey, @Aprillion. Thanks for the suggestion. That TypeScript error suppressed by "any" is not intended and is caused by the second argument that is a corrupted entity (on purpose). I think marking it with "expect-error" is precisely what that comment was designed to do. Would you like to open a pull request please? |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
PR #146 .. not sure why GitHub didn't link it automatically ¯\_(ツ)_/¯ |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I noticed
as anyassertions intest/utils/inheritInternalProperties.test.tsin #135, we could convert similar TS assertions to@ts-expect-errorfor an additional regression test of the types - if the production-code type was changed so that TS no longer produces an error, TS would complain about the missing error in the test code, e.g.:Beta Was this translation helpful? Give feedback.
All reactions