Reworked type hints

Backward incompatible changes

Arrays accepted null values implicitly without an option to disable null values. This behaviour has been changed so only non-null values are accepted now. If you require the acceptance of null values add null to the accepted item types of your array:

...
"myArrayProperty": {
	"type": "array",
	"items": {
		"type": ["string", "null"]
	}
}
...

Internal

• Changed some internal behaviour for a performance increase of the generated models (#12)
• Changed the generation process of merged properties so no unused code is generated (#13) (docs)

Bugfixes

• Arrays accept null entries implicitly
• RecursiveDirectoryIterator with a trailing slash results in a wrong base directory (#14)
• Wrong type hints for multi type properties and array properties