--
You received this message because you are subscribed to the Google Groups "OpenLMIS Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openlmis-dev...@googlegroups.com.
To post to this group, send email to openlm...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis-dev/0902b724-bbef-41a8-ac9e-5be21678e3e9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Thanks Paweł. Sounds quite promising. Can you share an example of the HTML output against the RAML in the requisitions repo?
Rich
To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis-dev/CAOKb-R5oFOCBS6ZTnyEZ1DjAPwpVqi80z%2BZcKDpegxH-x9zafw%40mail.gmail.com.
Great, thank you. One thing on my personal backlog is to update the “publish documentation” story so we can consolidate our API, ERD, style guide and any other doc via ReadTheDocs.
From: openlm...@googlegroups.com [mailto:openlm...@googlegroups.com]
On Behalf Of kkaczmarczyk
Sent: Tuesday, August 2, 2016 7:07 AM
To: OpenLMIS Dev <openlm...@googlegroups.com>
Cc: djaz...@thoughtworks.com; pnaw...@soldevelo.com
Subject: Re: [openlmis-dev] Generating static (offline) documentation for services' APIs
Just a follow-up on this one - static API document is published on each Jenkins build under the filename: "api-definition.html". It is visible in the Artifacts section of each build
--
You received this message because you are subscribed to the Google Groups "OpenLMIS Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
openlmis-dev...@googlegroups.com.
To post to this group, send email to
openlm...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis-dev/8f00901f-bc21-4256-8dee-4799269e13b8%40googlegroups.com.