[
https://issues.apache.org/jira/browse/FINERACT-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17236650#comment-17236650
]
Michael Vorburger commented on FINERACT-1263:
---------------------------------------------
This will be part of the PR
[https://github.com/apache/fineract/pull/1368/files] for FINERACT-1173, but
I'll keep the issue open, because the better real solution would be to be able
to fix the generated Swagger YAML, so that this is correct for non-Java clients
as well.
> /runreports Swagger missing optional R_* parameters
> ---------------------------------------------------
>
> Key: FINERACT-1263
> URL: https://issues.apache.org/jira/browse/FINERACT-1263
> Project: Apache Fineract
> Issue Type: Bug
> Components: SDK
> Reporter: Michael Vorburger
> Priority: Minor
>
> While working on and writing a Swagger client based integration test for
> FINERACT-1173, I've noticed that
> org.apache.fineract.client.services.RunReportsApi is generated wrong, because
> the Swagger metadata is missing a number of the parameters documented on
> [https://demo.fineract.dev/fineract-provider/api-docs/apiLive.htm#runreports.]
> The real solution would be to add the right Swagger annotations to
> org.apache.fineract.infrastructure.dataqueries.api.RunreportsApiResource.runReport(String,
> UriInfo, boolean), but I don't know how to do that for a Map<String,String>
> of arbitrary R_* parameters.
> I'll therefore "hack" the generated RunReportsApi class by "forking" it and
> suppressing it's regeneration, similar to what I've done e.g. for
> FINERACT-1227.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
