Unable to get options.configPath working

Is it possible to add a warning log when the custom config path does not exist? I am unable to troubleshoot why the jest angular builder cannot find my custom jest config.

The current custom-config.resolver.ts

static resolveForProject(projectRoot: Path, configPath: string){
  const jestConfigPath = getSystemPath(join(projectRoot, configPath));  
  return existsSync(jestConfigPath) && require(jestConfigPath) || {};
}

I propose adding:

console.log(`warning: unable to locate custom jest configuration at path "${jestConfigPath}"`);

The final code might look like:

static resolveForProject(projectRoot: Path, configPath: string){
  const jestConfigPath = getSystemPath(join(projectRoot, configPath));
  const exists = existsSync(jestConfigPath);
  if (!exists) {
    console.log(`warning: unable to locate custom jest configuration file at path "${jestConfigPath}"`);
    return {};
  }
  return require(jestConfigPath);
}

I would be more than happy to submit the PR myself if the concept is well received. Thanks!

[just-jeb]

Yeah, probably it should be displayed only in certain circumstances. The question is in which circumstances.
Indeed, if you don’t need custom config you’re fine. But if you do need it and you place it in a different place… You probably want to see this warning.
The builder hides complexity behind Jest setup. Part of it is that the user doesn’t have to specify config path explicitly - he can just use the default path and put the custom config under the directory specified in the docs. The builder, however, cannot distinguish between config path that was specified explicitly and the default one since the default comes from the JSON schema which is parsed by architect.
I’m open to suggestions though.

[denis-itskovich]

Why does this warning make sense? What if I don’t need custom config and the default one works fine? What if I configure custom configuration in package.json and not in jest.config.js?