Before You File a Proposal Please Confirm You Have Done The Following...

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

Relevant Package

typescript-estree

My proposal is suitable for this project

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

Description

Forwarding@fisker's#8136 (comment) here: right now, it seems there are three ways to turn offparserOptions.project in some way:

• false
• null
• []

That last one,[], is something I didn't know anybody was using (thanks@fisker for mentioning!). My interpretation ofparserOptions.project set to an array is that providing aproject array says explicitly that thereis a list of projects. So not providing any projects in that list means you'll never find the types. If there's no difference between that andfalse/null, then this is an ambiguity we need to at least document.

Proposal: as a breaking change for v7, if we see an empty array, perhaps we should throw an error (à la#6403) asking the user to either put projects in it, use v7's name forEXPERIMENTAL_useProjectService, or set it tofalse /null?

Additional Info

Adding to thev7 v8 milestone as we should really lock this down while we have the change to make breaking changes if needed.