chore: update type tests #2093
Merged
chore: update type tests #2093
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mrazauskas
commented
Apr 10, 2025
type-definitions/ts-tests/from-js.ts
Outdated
Comment on lines
36
to
39
| // eslint-disable-next-line @typescript-eslint/no-explicit-any | ||
| /* eslint-disable @typescript-eslint/no-explicit-any */ | ||
| const create = [(data: any) => data, fromJS][1]; | ||
|
|
||
| expect(create({ a: 'A' })).type.toBeAny(); | ||
| expect(create({ a: 'A' })).type.toBe<any>(); |
There was a problem hiding this comment.
Also lint rules apply for .toBe<any>(). That looks like a one more win, actually.
jdeniau
approved these changes
Apr 10, 2025
|
Thanks @mrazauskas |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Primitive type matchers like
.toBeString()or.toBeBoolean()will be removed in the next major TSTyche release. Reference: https://tstyche.org/releases/tstyche-4#matchersThis PR is replacing them with
.toBe().I think that
.toBe<number>()looks more constant. Makes it is easier to move from.toBe<number>()to.toBe<Promise<number>>(), if the behaviour is changing. It was not clear why using.toBeNumber()is anyhow better.