--p command line option should support taking a full path or directory.

[niemyjski]

This would allow you to specify a tsconfig.json that has a different name.

If you specify a directory, it should first try to resolve tsconfig.json. If it can't find it, it should find the first tsconfig*.json file

References: #2868 (comment)

[saschanaz]

• What benefit can we get when tsc automatically search tsconfig*.json files? What should happen when there are multiple tsconfig* files except tsconfig.json?
• Should tsc require any naming format? Should it allow project file without .json extension?

[zpdDG4gta8XKpMCd]

since my request #5705 got closed I am writing here:

• let's add a parameter that points to whatever configuration file we please: --configuration c:\foo\bar\myproject.csproj

[mhegazy]

let's add a parameter that points to whatever configuration file we please: --configuration c:\foo\bar\myproject.csproj

@Aleksey-Bykov can you elaborate on what is the expectation here? do you expect tsc to read the .csproj? where would the infrormation be stored?

[zpdDG4gta8XKpMCd]

i am saying the developer should be free to specify any file that has a valid tsconfig JSON content even if the name itself doesn't make any sense

[mhegazy]

i see, so why not use --project as in the OP?

[zpdDG4gta8XKpMCd]

because it's already taken it would be a breaking change

[mhegazy]

not really, we can check if it is a file path use it, if it is a directory append "tsconfig.json" before reading the file.

[zpdDG4gta8XKpMCd]

true, good catch

[RyanCavanaugh]

Thanks @saschanaz ! 🎉