Channels / #fineract / 2026-01-16

#fineract 2026-01-16

Fri 19:42Adam Saghy
Hey there,

I’m curious to know what topic or article you think would be the most suitable for me to write and share on my page: fineract-academy.com

I’d appreciate your recommendations!
👀 1
reply Fri 22:50kengne yvana
I think you should definitely include a section on Swagger UI. It’s really underrated because most people just see it as a list of documentation(from my point of view), but it’s actually a huge time-saver for debugging.
The main points I’d mention are:
  • It’s a shortcut for testing: Instead of clicking through the whole UI to find a bug, you can just go straight to the endpoint in Swagger and test the logic there. It helps you see instantly if the problem is in the backend code or just the frontend.
  • No more guessing JSON: It shows you exactly what fields the API needs. If you're working on something like the self-registration bug i am working on now, you can see the exact payload the server expects without digging through the Java code for hours.
  • It’s basically a 'Live Sandbox': Since it's built into Fineract, you don't have to set up Postman or anything else. You just open the link and start testing.
I think it would be great for the Academy because it helps beginners understand how the system actually talks to the database without getting lost in the UI.
Setting it up is easy, but there's one trick most people miss(I almost missed it, that's why i am pointing it out).
'Authorize' button at the top. You’ll need to put in your Fineract credentials (like `mifos`/`password`) and the Tenant ID (usually `default`).
That's why i am recommending this.
Please @Adam Saghy let me know what you think.
Thanks
👍 1
reply Thu 16:40Adam Monsen (meonkeys)
great stuff on there, @Adam Saghy! I really like the high-level explanations of what's happening during the build. As for what new content to create, maybe something that helps us clean up all the tech debt? Calling out bad/old practices we're trying to get rid of, in-progress migrations between design patterns, stuff like that (and pointing to JIRA tickets folks could work on)
👍 1
reply Thu 16:41Adam Monsen (meonkeys)
we just get that "which ticket should I work on" question so often, and cleaning up / conforming existing code is a helpful overall maintenance activity
👍 1
reply Fri 21:18Adam Saghy
2 merged, 1 tests are running
reply Fri 21:20kengne yvana
@Adam Saghy Thanks
reply Fri 22:07kengne yvana
The 3rd PR the tests are complete and successful.