v2.3.0

New overload of ToJson with serializer as parameter

v2.2.0

Added abstract base class for ObjectValue & SimpleValue

v2.1.0

Adding OperationId on Operations #7

v2.0.1

Fixing issue with subnaming of array items #9

v2.0.0

Version 2.0.0 change

In versions < 2.0, the Schemas were created based on simplified logic: If the schema is the same (having same structure), it is considered to be the same schema no matter name you use (actually the first parsed named is used for all others). This approach had good intentions - to minimize amount of created Schemas - however shown to be wrong for complex scenarios. This could easily lead to situation where change in one Schema breaks your other Schema, even if they were not directly linked using $ref.

Since version 2.0.0 the Schemas are created based on logic:

1. Root inline schemas are always created as separated one
2. Root $ref schemas are created as separated one but with structure "copied" from referenced schema
3. Nested inline schemas are created as separated one
4. Nested $ref schemas are linked to referenced schema

v1.6.0

• Fixing issue #6
• Setting dependencies for OpenAPIParser

v1.5.1

Fixing #5

v1.5.0

• Removed improper implementation of file watcher

v1.4.0

• Breaking Change: Enum values are real-ish enums

v1.3.0

• Enum values are checked when parsing