Michael Vorburger created FINERACT-838:
------------------------------------------
Summary: Swagger generated client libraries
Key: FINERACT-838
URL: https://issues.apache.org/jira/browse/FINERACT-838
Project: Apache Fineract
Issue Type: Sub-task
Reporter: Michael Vorburger
In the review discussion of the first Swagger PR
https://github.com/apache/fineract/pull/629 (which got superseded by
https://github.com/apache/fineract/pull/695), this came up:
{quote}The other plugin org.hidetake.swagger.generator is used to generate code
from the openAPI spec file using swagger-codegen. So this does not generate
response.json. It rather uses response.json to generate client code.{quote}
and {quote} think i had explained the usage of this in my gist
https://gist.github.com/kangbreder/034f47e2e8015cee10b48b7c5f1b8df1, generating
client libraries and language-specific SDKs in languages such as java and
angular from swagger specification file. This was part of the goals of the
project listed in
https://mifosforge.jira.com/wiki/spaces/RES/pages/812810251/Google+Summer+of+Code+2019+Ideas.{quote}
Having (Swagger automatically generate!) client libraries in Java (and even
other languages?!) seems like a cool idea. It's also something that perhaps
needs a bit more investigation than only adding the respective Gradle plugin.
If we actually do do this, after having done all of the work in the other Sub
Tasks, then I think we would have to include sample code in the repo building
against the generated client libraries to test and illustrate their usage. We
would also have to publish those client libraries, e.g. as downloadable JAR
from the release page (or later even made available on Maven central). It would
perhaps be clearest if there was another directory in the Fineract source tree,
next to and outside of not inside, the fineract-provider (which is the
"server") for this purpose.
[~kangbreder] [~awasum] [~sanyam] ([~sanyam96] ?) FYI
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
