-
Notifications
You must be signed in to change notification settings - Fork 459
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
Extract mocked function in a different package #1048
Comments
Maybe it can be exported under ts-jest/utils ? PR is welcome :) |
I think it's an excellent idea to either export it separately or extract it to its own package. PR's very welcome (or links to the new package, which we will then add to the docs.) |
Would it be worth proposing to the Jest team to add it to the core package, especially now that Jest is written in TypeScript, or to https://github.com/jest-community? |
might be worth a shot |
cc @thymikee do you think this can be in jest repo ? |
@SimenB what do you think? The question is whether we should include these utils in Jest core: https://github.com/kulshekhar/ts-jest/blob/master/src/util/testing.ts Personally I'm fine with sticking those to |
Yeah, works for me! Looks useful |
@ahnpnl let's create an issue for this in Jest first, shall we? |
Close as Feature Request was created for Jest |
Hello 👋
I have been using babel to compile my typescript projects more and more lately, and the only reason why I am still installing ts-jest is because of the
utils/mocked
function.Would you consider extracting this util into its own package?
The text was updated successfully, but these errors were encountered: