Bravado-core

------------------
- Fix optional enums in request params - `Issue 77`_
- Fix resolving refs during validation - `Issue 82`_

------------------
- More robust handling of operationId which contains non-standard chars - `PR 76`_
- Provide a client ingestible version of spec_dict with x-scope metadata removed. Accessible as Spec.client_spec_dict - `Issue 78`_

------------------
- Better handling of query parameters that don't have a value - `Issue 68`_
- Allow marshalling of objects which are subclasses of dict - `PR 61`_
- Fix boolean query params to support case-insensetive true/false and 0/1 - `Issue 70`_
- Support for Swagger specs in yaml format - `Issue 42`_
- Fix validation of server side request parameters when collectionFormat=multi and item type is not string - `Issue 66`_
- Fix unmarshalling of server side request parameters when collectionFormat=multi and cardinality is one - `PR 75`_

------------------
- Fix unmarshalling of an optional array query parameter when not passed in the
query string.

------------------
- Support for recursive $refs - `Issue 35`_
- Requires swagger-spec-validator 2.0.1
- Unqualified $refs no longer supported.
Bad: ``{"$ref": "User"}``
Good: ``{"$ref": "/definitions/User"}``
- Automatic tagging of models is only supported in the root swagger spec file.
If you have models defined in $ref targets that are in other files, you must
manually tag them with 'x-model' for them to be available as python types.
See `Model Discovery`_ for more info.

------------------
- Fix the creation of operations that contain shared parameters for a given endpoint.