@saurabh We had this resource in openmrs-1.8 as SystemInformation resource, which is directly fetching the system information from AdministrationService.
We refactored the Swagger documentation in early 2019 and it seems like this resource didn’t get updated with that change. That’s why we can’t get it over our Swagger documentation.
@ayesh I tested this endpoint /systeminformation for a GET request and it works so should I add this to the documentation as well along with small description of the “SystemInformation” that you suggested??
and @suthagar23 as far as I can infer from the code snippet you shared this resource just supports only one operation that is getAll , am I missing something ??
@ayesh I have java code for Base64 authorization. It is in plain java. If you think it is usable. I can make a pr. I was trying to use openmrs SDK to build an OWA to make REST API requests, but I am have some difficulty.
We need java client samples calling the rest api we have not sdk samples. Here we are building a documentation web site not code playground so no sdk code it’s about simple java get post request froma client to the rest api
@ayesh should we add proper curl examples as well since they can be easily derived fromt the current http calls and they are pretty easy to run for anyone straight from the command prompt ??
and as a part of testing the previous examples I have tested several of them uptill now so will it be useful to add them along the language tabs ?
So if you look in most of the documentation of current opensource products they have documented the curl calls as we have in the examples. It’s a language-agnostic way of defining the endpoint for developers to understand.
I don’t see a need to change them to curl examples for now. The best would be to continue and achieve the same examples in java in the new tab that you are working currently.