Releases: goldspecdigital/oooas
Releases · goldspecdigital/oooas
v2.4.1
Fixed
- Properties that should accept numeric (integer and float) values , but only allowed integers, now allow for both integers and floats.
v2.4.0
Added
- Added
formUrlEncoded()
creation method inMediaType
object (forapplication/x-www-form-urlencoded
request bodies).
v2.3.1
Changed
- The branching strategy no longer makes use of the
develop
branch. Instead all feature/hotfix branches should be based off ofmaster
. - The composer
test
script now makes reference to the individualtest:style
andtest:unit
scripts.
Fixed
- The test suite PSR-4 autoloading has now been moved to
autoload-dev
within thecomposer.json
file.
v2.3.0
Added
- The
toJson()
method now allows you to specify the$options
parameter to proxy to thejson_encode()
function.
v2.2.0
Added
$ref
can now be used in place of all objects.- The
Components
object now supports all fields (with exception to callbacks).
Changed
- The
create()
static method has now been moved to theBaseObject
class with a return type also beingBaseObject
. If you are extending any object classes and overriding thecreate()
method, then be sure to update your return type. DocBlock type hinting has been provided to indicate a static return type, so your IDE should still be able to provide autocompletion for child class members.
Fixed
- Description updated in
composer.json
. - Linter commands are now using cache when called in the
composer.json
scripts.
v2.1.0
Added
- You can now specify on an
Operation
object that it should not have any security by invoking thenoSecurity()
method on an instance of it.
v2.0.1
Fixed
- The
SecurityRequirement
object now accepts a singleSecurityScheme
along with an array of scopes. This is because it was outputting incorrect data, and its purpose was misleading. It now acts as a way to specify a singleSecurityScheme
along with any scopes. Any object that accepts aSecurityRequirement
object, always accepts an array of them, so you can still specify severalSecurityScheme
objects by wrapping them in aSecurityRequirement
.
v2.0.0
Added
- The
Response
class now has helper methods for common HTTP responses. - Missing object from the OpenAPI spec have had their corresponding classes added.
- Support added for the OpenAPI
3.0.2
spec. - Test cases for each object class.
Changed
- Object class constructors (and
create()
methods) now only accept the optional$objectId
parameter which is used in several scenarios. - Removed
Paths
class and instead theOpenApi
class has a variadicpaths()
method which takes any number ofPathItem
instances. - Class constants now have their name prefixed with the property it is intended to be used with.
Fixed
- The
OpenApi
class is now immutable like all the other object classes.
v1.0.2
Fixed
- Corrected typo in name, from Orientated to Oriented.
v1.0.1
Fixed
- Provided a much simpler example in the
README.md
.