Extract/Expose schemaToHTML (and others) #486
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Jun 12, 2015
ponelat
force-pushed
the
fix/render-responses
branch
from
7d61a89
to
f3588bd
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Connected to swagger-api/swagger-ui#1368
Well, this is the first step in getting the rendering/markup of swagger-js schems out of swagger-js.
It is a big merge.
lib/types/model.js, and all markup logic fromlib/helpers.jsinto its own file...lib/schema-markup.jsschema-markup.js is a now standalone (uses a touch of
lib/helpers.js) which renders markup and JSON samples from a schema and/or a Model object.From here on, we can move
schema-markupinto swagger-ui and perhaps make it into a collection of handlebar templates.