Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/typescript-eslint/typescript-eslint/issues/7384 below:

Enhancement: Allow parserOptions.project to be (true

• I have searched for related issues and found none that match my proposal.
• I have searched the current rule list and found no rules that match my proposal.
• I have read the FAQ and my problem is not listed.

parser

• I believe my proposal would be useful to the broader TypeScript community (meaning it is not a niche proposal).

In #6084 we added the ability to specify parserOptions.project: true. Doing so indicates each file should be linted with the closest tsconfig.json to that file.

But, what if a repo wants a different TSConfig for files that it matches, and true for all other files? For example, maybe it'd want:

• tsconfig.eslint.json to apply for *.(c)js files
• tsconfig.json for all other files

What if we allow specifiers like project: ['tsconfig.eslint.json', true]? In essence, this would be allowing configs to include true inside the already-present string[] option that says to find the first matching TSConfig.

Example repro case here: https://github.com/JoshuaKGoldberg/repros/tree/typescript-eslint-parserOptions-project-string-true

Somewhat of a sibling issue to #7383. If we end up allowing an object with a type name then this issue would be to change project to (boolean | string | ThatNewProjectSpecifierType)[].

Zamiell, bryan-hoang, so1ve, reduckted, veimox and 4 moresilvenon

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4