Release 1.1.6

Diff: 1.1.5...1.1.6

Fix:

• PHPUnit must be >=4.8 <6.0

Enchancement:

• Test: Add testSetSecurityForOperationSuccess
• Improve debug info about require property doesnot exist
• Composer: Bind latest patch release of zircote/swagger-php
• Introduce Swagger version check (only 2.0 supported)

Release 1.1.5

Feature:

Introduce: setSecurityForOperation, see 721506e

Release 1.1.4

Hotfix:

• Hotfix: addParametersFromSecurity - check unique on next calls, see 6d7d67d

regression after aba05d4

Release 1.1.3

Fixes:

• Hotfix: addParametersFromSecurity on assertHttpResponseForOperation

$operation = self::$swaggerWrapper->getOperationByName('getUserById');
 /**
  * This operation does not require Security
  * We change operation to require it, see X-AUTH-TOKEN in parameters
  */
$operation->security = [['jwt' => []]];

Now, call on assertHttpResponseForOperation will:

// User can mutate Operation->security, and we should re-enable it
if ($path->security) {
   $this->addParametersFromSecurity($path);
}

Release 1.1.2

Enchancement:

• Write Response->content on bad responses, see 348561f

Release 1.1.1

• Hotfix: Use array_key_exists, because isset will return false on null

This was caused, when you pass null inside parameters, example:

$this->makeRequestByOperation(
     $operation,
     [
          'limit' => null,
     ]
);

Release 1.1.0

Add addition check for Zend/Laravel/Symfony trait helpers:

• Parameter '{$parameter}' passed, but does not exist in request definition (swagger)

1.0.4

Release 1.0.4

Release 1.0.3

Hotfix:

• validateScheme - skip schema without properties (notice)

Release 1.0.1

• Fix: Null checks must be done on nullable === false