Skip to content

fix: add setSerializers and defaultSerializers to TS types #95

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

Merged
merged 1 commit into from
Nov 5, 2019

Conversation

thymikee
Copy link
Member

@thymikee thymikee commented Nov 5, 2019

Adding missing TS types for setSerializers and defaultSerializers

cc @SimenB can you test that?

@SimenB
Copy link
Member

SimenB commented Nov 5, 2019

I'm unable to upgrade due to the changes in #92. That DefinitelyTyped/DefinitelyTyped#39243 was released is pretty weird to me, it's super breaking...

Anyway, the changes here looks great 👍

@thymikee thymikee changed the title fix: add setSerializers and defaultSerializers to TS types fix: add setSerializers and defaultSerializers to TS types Nov 5, 2019
@thymikee thymikee merged commit 992a35c into master Nov 5, 2019
@thymikee thymikee deleted the fix/ts branch November 5, 2019 09:55
@thymikee
Copy link
Member Author

thymikee commented Nov 5, 2019

Is it possible for TS to override the interface to be compatible with the older version of @types/jest? If not, please let me know if you have ideas on how we could support both interfaces for Matchers

@SimenB
Copy link
Member

SimenB commented Nov 5, 2019

I don't know... IMO @types/jest should be reverted, it's way too breaking. But I haven't really looked into it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants