The second example in section 1.1 says:

expect(result.approved).to.be.false;

It should be:

expect(result.approved).to.be.true;

(I'm guessing you made it false so you could simulate the error output in the next picture.)

Basically we need to choose between:

class X {

  private $foo;

  public function __construct(string $foo) {
    $this->foo = $foo;
  }

  public function getFoo(): string {
    return $this->foo;
  }
}

or:

class X {

  /**
   * @var string
   */
  private $foo;

  public function __construct(string $foo) {
    $this->foo = $foo;
  }

  public f

Description

The following code snippet should throw even when process.env.NODE_ENV is set to production because the Proxy set handler returns a false. However JSC has a known issue where the Proxy doesn't throw a TypeError if the retur

add salting to the hashes obfuscator generates.

If you are running your tests in watch mode by default (Jest or similar) you have your tests doing nothing forever when mutode is trying to run them.
It'd be great to have mutode realise this and warn the user, or perhaps set itself up to run common test runners in CI mode.

Bug description

SonarCloud always report 0% coverage

Expected behavior

SonarCloud should report the right coverage.

How to reproduce

Build an internal branch/PR on Travis CI.

Additional context

It looks like Sonar team has deprecated usage of JaCoCo's .exec files and doesn't take them into account anymore. [Here](https://community.sonarsource.com/t/coverage-test-

Example

upsert({
  update: {
    role: 'ADMIN'
  },
  where: {
    email: 'alice@prisma.io'
  },
  create: {
    name: 'Alice',
    email: 'alice@prisma.io',
    role: 'ADMIN'
  }
})

Readme is not easy to keep in sync with library updates as it is always the latest version which is shown.