V2 rewrite

[trieloff]

This is still a work in progress of what will become an effective re-write of jsonschema2md

Some of the changes that are coming:

• optimist (unmaintained) replaced with yargs
• bluebird, lodash replaced with ferrum
• i18n (with unmaintained dependencies) replaced with es2015-i18n-tag
• replaced ejs templates with mast-builder (Switch from EJS templates to Unist-Builder? #126 and broken ejs results in empty source file #174)
• root schemas can be of any type now (fixes Am I correct that the root type can only be object? #73 and refs in items of array do not work at root level #72)
• support for "join types" with anyOf, oneOf, allOf, and not (Unknown type for array with anyOf items #94 and The generator does not handle allOf/anyOf/oneOf properly if schemas include properties, and are not references. #52 and Support not keyword #20)
• schemas can be nested up to any level you'd like (an array of objects within an array of objects within…) fixes Change directory layout to enable separate output files for nested objects? #125
• better support for type arrays Type Arrays not Supported #177
• schemas are no longer validated

Some things will be made easier with the change:

• Optionally increase heading level #118
• Schema Hierarchy lists all references, not just inclusions #34

And some things will be made impossible:

• Custom template override #123

but this is still work in progress and a couple of things remain to be done:

• replace jasmine with mocha and measure code coverage
• bring code coverage up to 100%
• support additionalProperties additionalProperties currently only works as a boolean. #95
• support additionalItems Handle additionalItems and arrays that specify schema order. #31
• support patternProperties Nested Pattern Properties ignored #180
• provide German translation (en is default locale)
• create JSON schema output

[trieloff]

🎉 This PR is included in version 4.0.0 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)

Your semantic-release bot 📦🚀

[Relequestual]

What's meant by "schemas are no longer validated"?
Is this in relation to #100 ?

[trieloff]

We used to have a dependency to ajv and used ajv to validate the schemas before we would even try to generate documentation. This brought a couple of drawbacks like:

• additional dependencies
• additional processing time
• you needed to specify the JSON Schema version you were using

for very little benefit.

In order to implement #100 and generate the list of supported and unsupported keywords (https://github.com/adobe/jsonschema2md/blob/master/schemasupport.md) I've tagged every use of a keyword in the code with keyword and wrote a test that compares the keywords that have been used against the keywords that are mentioned in the spec. This does not rely on schema validation at all.

[Relequestual]

I hadn't realised you had made the jump to draft 2019-09! Very exciting!
From previous discussions and this, I think what you've developed would be a great candidate for creating a vocabulary.
Obviously it's a little tricky to create and test out addtional vocabulaires with so few implementations, but they will come. =]
You have my email. Feel free to reach out should you want any feedback or sounding board for ideas!