You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Errors matched by .toRaiseError() should not be highlighted in code editors. This must work similar to the // @ts-expect-error comment, but should take into account provided substring or error code.
The text was updated successfully, but these errors were encountered:
I was looking through some type tests. Mostly .toRaiseError() is used to make sure that a property does not exist on a type or that a function cannot be called with certain arguments. Hm.. What about .not.toHaveProperty() and .not.toBeCallableWith() matchers?
For my eye the new matchers are better solution than silencing errors via language service. Also because the matcher will make it possible passing a file through tsc compiler (see #13).
The new .toHaveProperty() matcher just shipped with TSTyche 1.0.0-beta.6. Give it a try.
Errors matched by
.toRaiseError()
should not be highlighted in code editors. This must work similar to the// @ts-expect-error
comment, but should take into account provided substring or error code.The text was updated successfully, but these errors were encountered: