-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[typescript] Add T
param to Matchers interface
#1620
Conversation
🦋 Changeset is good to goLatest commit: b753cbf We got this. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
@spudly if this is a requirement (to parameter count to match) - isn't this a breaking change (sort of) for people using older version of jest (or its typings)? |
Yes, good point. I guess I'll have to change the changeset...
…On Fri, Nov 8, 2019, 5:06 PM Mateusz Burzyński ***@***.***> wrote:
@spudly <https://github.com/spudly> if this is a requirement (to
parameter count to match) - isn't this a breaking change (sort of) for
people using older version of jest (or its typings)?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1620?email_source=notifications&email_token=AADW5HFQYVVBHG2NX6UCUSLQSXPGJA5CNFSM4JKX5T52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDTPQ3Q#issuecomment-552007790>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADW5HEV3QGOS2SKMQ6SGG3QSXPGJANCNFSM4JKX5T5Q>
.
|
You can target |
Does the dependency on "@types/jest" need to be bumped too? |
Yes, that would require updating as well. @spudly will you have time to address the code review comments? |
Made the requested changes. Ready for review again. |
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit b753cbf:
|
sorry, had conflicts. resolved. |
Fixes type definition issue when using jest-emotion with jestv24 See DefinitelyTyped/DefinitelyTyped#39982
Thanks for this! I should merge this soon. As a point of reference for anyone interested in this - cc @JakeGinnivan just as a confirmation - such change is OK as we should get ourselves up-to-date and there is no way to support both, right? I've tried searching if this can somehow be overloaded to match both, but couldn't find a way. |
Co-Authored-By: Mateusz Burzyński <mateuszburzynski@gmail.com>
This fixes typescript type definitions when using jest-emotion with jest 24.
I simply added a parameter to the Matchers interface in the typescript types file for jest-emotion.
In Jest 24 they added a second generic parameter to the
Matchers
interface. Typescript requires interfaces to have the same parameters, so jest-emotion needs to add it also.See DefinitelyTyped/DefinitelyTyped#39982
Checklist: