Referenced TypeAliases

[WoH]

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?
• Have you written unit tests?
• Have you written unit tests that cover the negative cases (i.e.: if bad data is submitted, does the library respond properly)?
• This PR is associated with an existing issue?

Closing issues

Closes #204

If this is a new feature submission:

• Has the issue had a maintainer respond to the issue and clarify that the feature is something that aligns with the goals and philosophy of the project?

Potential Problems With The Approach

Test plan

Generated validation models look good to me, I added some props to the validation model to indicate what we can do now.

Ideal test plan would be:

• alias a string with validation
• alias a number with validation
• maybe alias a date with validation
• maybe alias union/intersection
• alias a union of a model and an alias with validation on the alias
• alias nestedObjectLiteral with validation on a property within the nOL
• generic type alias

For each of these:

• Definition: Description
• Definition: Example
• Definition: type is $ref
• Definition: Model is fine
• Validation: Validates
• Validates: invalidates

This is why this will probably take me a long time and I'd be super grateful if someone could contribute parts of that.

Opened a second pull request based on #475 .
To view only this PR without dependencies, use GitHub's filter commits feature. (Similar to this, but filter commits (left) instead of files (middle)).

Todo:

• Test plan
• Merge Generics: Use %-encoded escaped names to prevent clashes #475
• Refactor legacy reference checking based on properties to check on kind instead.
• Test implementations

[WoH]

Generated validation models look good to me, I added some props to the validation model to indicate what we can do now.

Ideal test plan would be:

• alias a string with validation
• alias a number with validation
• maybe alias a date with validation
• maybe alias union/intersection
• alias a union of a model and an alias with validation on the alias
• alias nestedObjectLiteral with validation on a property within the nOL.
• generic type alias

For each of these:

• Definition: Description
• Definition: Example
• Definition: type is $ref
• Definition: Model is fine
• Validation: Validates
• Validates: invalidates

This is why this will probably take me a long time and I'd be super grateful if someone could contribute parts of that.