[
https://issues.apache.org/jira/browse/FINERACT-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Vorburger reopened FINERACT-1480:
-----------------------------------------
[~ptuomola] do you mind if I re-open this? Both
[https://demo.fineract.dev/fineract-provider/swagger-ui/index.html] and
[https://demo.fineract.dev/fineract-provider/swagger-ui/fineract.yaml] are
still broken, even after the PR with the supposed fix has been rolled out, note
that [https://demo.fineract.dev/fineract-provider/actuator/info] is currently
at 515440e239b4dce692c37cd6abb6a9113831b82d which is after
4d879eddc469f3fdb8b1d0608525c89d0ec0de12 from
[https://github.com/apache/fineract/pull/2018]. I've not looked further into
why, but thought that this may interest you.
> Swagger UI is broken (because fineract.yaml moved?)
> ---------------------------------------------------
>
> Key: FINERACT-1480
> URL: https://issues.apache.org/jira/browse/FINERACT-1480
> Project: Apache Fineract
> Issue Type: Bug
> Affects Versions: 1.6.0
> Reporter: Michael Vorburger
> Assignee: Petri Tuomola
> Priority: Blocker
> Fix For: 1.6.0
>
>
> While testing https://github.com/vorburger/www.fineract.dev/issues/11 and
> following the first links mentioned on https://www.fineract.dev, namely
> https://demo.fineract.dev/fineract-provider/swagger-ui/index.html (as well as
> https://demo.fineract.dev/fineract-provider/swagger-ui/fineract.yaml) I have
> noticed that the Swagger YAML and thus UI has recently been broken.
> It's curious that the
> https://github.com/apache/fineract/blob/develop/integration-tests/src/test/java/org/apache/fineract/integrationtests/SwaggeruiTest.java
> did not catch this regression. It would be nice if this were addressed as
> part of fixing this. Would it perhaps suffice to add a {{GET
> /fineract-provider/swagger-ui/fineract.yaml}} (in addition to {{index.html}})
> to that test? Or is it a (Docker) Container Image specific regression?
> [~ptuomola] or [~aleks] or maybe [~Manthan] perhaps digging into and finding
> a solution for this interests you, or you want to point anyone at this issue.
> (I won't be working on this, I'm just filing issues for what I find in the
> Fineract.dev logs.)
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
