Compatibility to draft 07

[netanel-mce]

what is here

• new flag compatibility to choose if output schema must to match to draft 07, if draft-07 is chosen, so:
  • undefined is not a valid for definition.type, so:
    • if main type is alias of undefined - we will throw error
    • if have a property undefined - we will ignore (like never)
  • symbol is not a valid for definision.type, so we write object instead
  • we not using in the operator typeof for definition.type only after check what returned from he
• new type DefinitionTypeName for save on definition.type
• unit test with compatibility draft-07 and none
• updating README.md file
• updating api.md file
• fix issue: #490

[domoritz]

Thanks for the pull request. I think I prefer not to have an option and to just make compatibility with a newish draft the default. What do you think?

[netanel-mce]

@domoritz Hello My PR currently throws errors when TSJ is enforced to generate non-standard schema, like top-level "undefined" which is strange, and unparsable by standard JSON schema validators. (like AJV) If that's acceptable, then I'll be happy to submit this PR without the switch.

[domoritz]

I'm not following. Are you saying that we get errors if we generate non-standard schemas and that we currently do create those schemas? In that case I would strongly vote for making standard compliant output the default without a switch.

[netanel-mce]

@domoritz Yes, that's the situation today, I'll remove the switch

[netanel-mce]

I'm not following. Are you saying that we get errors if we generate non-standard schemas and that we currently do create those schemas? In that case I would strongly vote for making standard compliant output the default without a switch.

@domoritz done, all schemas should compatibility to draft-07.

[domoritz]

Thank you