Hello Michael
The swagger specification file is the response.json file. All the resource
classes are only used to add swagger annotations on each endpoint and for
model classes.
At build time, the swagger specification is generated at
I'd also be interested to follow along re. this, but I can't seem to find a
PR re this on https://github.com/apache/fineract/pulls .. what am I missing?
I briefly looked at
Hi Abhay,
Please report an issue related to the community app and the submit button.
We update the demo server to be on the latest stable release so if you need
the bleeding edge code, you can access that from the staging server.
Addressing the stability issues on demo server is ongoing.
Ed
Update: Regarding #1 while working with the staging server in the new web
app I was able to add a charge and update the share product. The issue must
have been resolved. The staging server is more recently updated than the
demo server. At https://staging.openmf.org though the submit button doesn't
I think Ebenezer Graham works at the Backend too.
On Mon, Aug 5, 2019 at 11:59 AM Kang Breder wrote:
> Hi Cajetan
>
> Find the path below for self client Api Resource
>
> fineract/fineract-provider/src/main/java/org/apache/fineract/portfolio/self/client/api/SelfClientsApiResource.java
>
> On
Hi Cajetan
Find the path below for self client Api Resource
fineract/fineract-provider/src/main/java/org/apache/fineract/portfolio/self/client/api/SelfClientsApiResource.java
On Mon, Aug 5, 2019 at 11:09 AM Cajetan Rodrigues
wrote:
> Can you please point a repo where the self-service APIs are
Can you please point a repo where the self-service APIs are being created
and also let me know who else is working on the backend other than you, so
I get in touch with them.
Thanks and Regards,
*Cajetan Christopher Rodrigues*
*B.E Computer Engineering*
*rigrod1...@gmail.com *
*Google Summer of
Hi all,
I had two queries regarding the products section.
1) While editing a share product whenever I add a charge and try to submit,
It gives me an unknown error. I was able to reproduce this on the demo
server. @Santosh Math seems to be a
backend issue.
2) We have existing APIs for deletion
