vorburger commented on a change in pull request #1163:
URL: https://github.com/apache/fineract/pull/1163#discussion_r453987711



##########
File path: fineract-provider/config/swagger/fineract-input.json
##########
@@ -0,0 +1,16 @@
+{
+  "openapi" : "3.0.3",
+  "info": {
+    "version": "1.4.0",
+    "title": "Apache Fineract",
+    "description": "Apache Fineract is a secure, multi-tenanted microfinance 
platform\n\nThe goal of the Apache Fineract API is to empower developers to 
build apps on top of the Apache Fineract Platform<br>The [reference 
app](https://cui.fineract.dev) (username: mifos, password: password) works on 
the same demo tenant as the interactive links in this documentation\n\n- The 
API is organized around 
[REST](https://en.wikipedia.org/wiki/Representational_state_transfer)\n- Find 
out more about Apache Fineract 
[here](/fineract-provider/api-docs/apiLive.htm#top)\n- You can [Try The API 
From Your Browser](/fineract-provider/api-docs/apiLive.htm#interact)\n- The 
Generic Options are available 
[here](/fineract-provider/api-docs/apiLive.htm#genopts)\n- Find out more about 
[Updating Dates and 
Numbers](/fineract-provider/api-docs/apiLive.htm#dates_and_numbers)\n- For the 
Authentication and the Basic of HTTP and HTTPS refer 
[here](/fineract-provider/api-docs/apiLive.htm#authentication_overview)\n- 
Check about ERROR codes 
[here](/fineract-provider/api-docs/apiLive.htm#errors)\n\nPlease refer to the 
[old documentation](/fineract-provider/api-docs/apiLive.htm) for any 
documentation queries",
+    "termsOfService": 
"https://demo.fineract.dev/fineract-provider/api-docs/apiLive.htm";,

Review comment:
       Is it possible to just leave this out entirely? Or use 
/fineract-provider/... without fineract.dev hostname?




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to