Expose project matching behaviour · jestjs/jest#11171

(2 留言) (0 反應) (0 負責人)TypeScript (45,361 star) (6,653 fork)batch import

:rocket: Feature RequestHelp WantedPinned

描述

🚀 Feature Proposal

Expose the logic that determines what project a file belongs to. Given a file path and a Jest configuration, what options apply?

Motivation

To allow third-party tools to understand Jest configurations. E.g: https://github.com/jest-community/eslint-plugin-jest/pull/754#issuecomment-780396777

Example

I am not sure what package this logic currently resides in, but something along the lines of:

import { resolveOptions } from '@jest/options';
import { readConfig } from '@jest/config';

const config = await readConfig('/path/to/jest.config.js');
const options = await resolveOptions('/path/to/unit.test.js', config);

Pitch

The projects logic is very specific to Jest, and recreating it externally would likely be erroneous and fall out-of-date quickly.

貢獻者指南

技術棧: typescriptnodejs
領域: apitestingdeveloper experience
議題類型: feature
難度: 3
預計時間: 1-2 days
活動狀態: stale
清晰度: needs investigation
前置要求: Understanding of Jest's project matchingFamiliarity with Jest's configuration system
新手友善度: 25
研究方向: Investigate the current implementation of project matching in Jest, likely in packages like jest config or jest core. The issue references a related PR in eslint plugin jest. Look at the link provided for context on what third party tools need. Determine where the logic resides (e.g., resolveOptions) and plan to export it via a new package like @jest/options. Examine existing config reading code to ensure the API is flexible enough.