-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Document the "official" type for what should be exported from jest.config.js #9529
Comments
In theory it's |
@SimenB that seems to work pretty well. One thing of note: i.e
Would it be alright if I opened a PR changing this? |
Yeah, sure 👍 |
@G-Rath close this? |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
🚀 Feature Proposal
I feel a bit foolish asking this as in theory it should be somewhat obvious & easy...., but I can't figure out what type to use for the export of
jest.config.js
for TypeScript(-in-js) 😬i.e with
.eslintrc.js
I can do:But for Jest theres a couple of different interfaces, each with their pros and cons: there's
Project
&Global
, some with required properties, and others all optional, and then theres the normalised values...I think it would be good to mark a type/interface as The Public Configuration Type, and put a line on the Configuring Jest page.
Motivation
This would let us be nice and type safe when configuring jest :D
It would also mean we'd not be having to use external schemas that need to be updated by third-parties.
Example
Pitch
Because it's already in the core... somewhere... 🕵
The text was updated successfully, but these errors were encountered: