Nested Objects

[Sergej-Popov]

Add support for nested object Schema for objects that are not Dictionaries.

#8 has introduced nested schemas. But it only accounted for Dictionaries: objects with arbitrary keys. This was a little design mistake since there was no nice way to address nested Objects with defined schema. This PR changes dictionary syntax to use DictionarySchema<T> and reserves nested Schema<T> for structured objects.

Since the change is breaking - the major version of the package is increased.

Type of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

All Submissions:

• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?
• I have updated the documentation accordingly.

New Feature Submissions:

• Does your submission pass tests?
• Have you lint your code locally prior to submission?

Changes to Core Features:

• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your core changes, as applicable?
• Have you successfully run tests with your changes locally?

[TomFreeman]

Just to see if I understand this at all 😄

It seems this line is giving us the ability to delegate to the compile method which properties to return. Which lets the compile method for the DictionarySchema select not to use the additionalProperties property...

[Sergej-Popov]

Yes, that's correct. Should have never been part of array-schema logic but I didn't see it at the time.

[TomFreeman]

Looks okay to me.

I'm not going to pretend I understand how the fix works 😄

[Sergej-Popov]

Added a bit more info in Wiki to explain the difference between normal object & dictionary
https://github.com/justeat/ts-jsonschema-builder/wiki/Object