Created by: man-at-home
PR checklist
- [x ] Read the contribution guidelines.
- [ x] Ran the shell script under
./bin/to update Petstore sample so that CIs can verify the change. (For instance, only need to run./bin/{LANG}-petstore.sh,./bin/openapi3/{LANG}-petstore.shif updating the {LANG} (e.g. php, ruby, python, etc) code generator or {LANG} client's mustache templates). Windows batch files can be found in.\bin\windows\. If contributing template-only or documentation-only changes which will change sample output, be sure to build the project first. - [ x] Filed the PR against the correct branch:
master,4.1.x,5.0.x. Default:master. -
Copied the technical committee to review the pull request if your PR is targeting a particular programming language.
Description of the PR
- added a basic asciidoc markup documentation generator (oriented on html or cwiki)
two advantages:
- a) printable output for openapi specs (pdf, more options via docbook)
- b) generator allows to augment (include or link) the generated documentation with other outputs via mustache filters
- augmenting info would be: sample output by spring restdoc, hand written spec prose and in this case wiremock sample data generated by spring boot cloud contract
technical commitee: (core team as asciidoc markup has no team)
@wing328 @jimschubert @cbornet @ackintosh @jmini @etherealjoy