leejo / swagger2-markdown / 21 / 6
100%
master: 100%

DEFAULT BRANCH: master
Ran
Files 2
Run time 0s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 100.0%. Remained the same
21.6

push

travis-ci

leejo 
resolve #1 - add basic markdown output

Squashed commit of the following:

commit e2538b9e8
Author: Lee Johnson <lee@givengain.ch>
Date:   Fri Sep 25 11:06:21 2015 +0200

    test for a swagger file to markdown with no x-api-blueprint

    shows that the markdown is output nicely with no line breaks to make
    the codified sections break

commit c91982440
Author: Lee Johnson <lee@givengain.ch>
Date:   Fri Sep 25 10:52:30 2015 +0200

    stop Pod::Markdown escaping reserved md chars

    as we can have literal markdown in the swagger config (as part of
    descriptions and such) so we *don't* want to escape it in output

commit b664ab56a
Author: Lee Johnson <lee@givengain.ch>
Date:   Fri Sep 25 10:31:56 2015 +0200

    fix encoding warnings in call to Pod::Markdown

    use the match_encoding flag, had to fix a couple of swagger test
    specs to replace the – char with -

commit 04a2624d3
Author: Lee Johnson <lee@givengain.ch>
Date:   Tue Sep 1 13:53:07 2015 +0200

    resolve #1 - generate basic markdown output

    delegate to the Pod::Markdown module using the ->pod->to_string
    methods of Swagger2. TODO: the markdown generated by this doesn't
    quite look right as some of the markup is escaped, possibly need
    to pass arguments to the markdown parser and/or post process the
    generated markdown string before output

commit bfc92aba0
Author: Lee Johnson <lee@givengain.ch>
Date:   Tue Sep 1 13:23:20 2015 +0200

    ref #1 move markdown directory to api_blueprint

    as we will be creating a test to generate basic markdown so these
    should be in a clearly named directory

26 of 26 relevant lines covered (100.0%)

7.88 hits per line

Source Files on job 21.6