( configFile: string, extendsValue: string, host: ConfigurationHost, fs: FileSystem, )
| 190 | } |
| 191 | |
| 192 | function getExtendedConfigPath( |
| 193 | configFile: string, |
| 194 | extendsValue: string, |
| 195 | host: ConfigurationHost, |
| 196 | fs: FileSystem, |
| 197 | ): AbsoluteFsPath | null { |
| 198 | const result = getExtendedConfigPathWorker(configFile, extendsValue, host, fs); |
| 199 | if (result !== null) { |
| 200 | return result; |
| 201 | } |
| 202 | |
| 203 | // Try to resolve the paths with a json extension append a json extension to the file in case if |
| 204 | // it is missing and the resolution failed. This is to replicate TypeScript behaviour, see: |
| 205 | // https://github.com/microsoft/TypeScript/blob/294a5a7d784a5a95a8048ee990400979a6bc3a1c/src/compiler/commandLineParser.ts#L2806 |
| 206 | return getExtendedConfigPathWorker(configFile, `${extendsValue}.json`, host, fs); |
| 207 | } |
| 208 | |
| 209 | function getExtendedConfigPathWorker( |
| 210 | configFile: string, |
no test coverage detected
searching dependent graphs…