New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Markdown supported in swagger-editor but not swagger-codegen #1203
Comments
@joe-kahuna you're correct in saying that the codegen won't do anything with markdown when generating the static documentation and we would definitely welcome your contribution with a PR to support that. You might also want to take a look at https://github.com/Swagger2Markup/swagger2markup to see if it meets your requirement. |
I'm not going to get to a markdown converter within codegen anytime soon. Joe On Tue, Sep 8, 2015 at 8:55 PM, wing328 notifications@github.com wrote:
Joe Malin |
Understood and glad to hear that swagger2markup works for you. |
This addresses swagger-api#4611 Replace {{description}} with {{unescapedDescription}} This is an improvement but because of issue swagger-api#1203 and/or swagger-api#3436 (fix not yet impleented), Markdown is not being processed and converted to HTML.
* Use {{unescapedDescription}} in html, html2 This addresses #4611 Replace {{description}} with {{unescapedDescription}} This is an improvement but because of issue #1203 and/or #3436 (fix not yet impleented), Markdown is not being processed and converted to HTML. * Add generated petstore samples index.html * Copy unescapedDescription
…-api#4641) * Use {{unescapedDescription}} in html, html2 This addresses swagger-api#4611 Replace {{description}} with {{unescapedDescription}} This is an improvement but because of issue swagger-api#1203 and/or swagger-api#3436 (fix not yet impleented), Markdown is not being processed and converted to HTML. * Add generated petstore samples index.html * Copy unescapedDescription
I can use Markdown in several places in my API spec (in YAML) to enter detailed descriptions, and swagger-editor will interpret it and display it correctly. However, when I put the resulting spec (in JSON) into swagger-codegen, it doesn't convert the markdown while generating a static HTML page. As far as I can tell, swagger-codegen doesn't accept YAML, so the end result is that I have to do extensive reformatting to convert my spec to HTML documentation. This has to be fixed.
The text was updated successfully, but these errors were encountered: