You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The SolrWayback frontend is separated from the backend using well defined webservice endpoints. As these endpoints can also be used by other applications, such as dashboards of analysis tools ("notebooks"), they should be properly defined with description, sample arguments etc.
OpenAPI is the obvious choice and writing a proper YAML for the existing endpoints seems like a straight forward task. However, switching it around so that the webservice specific parts of the code base is generated by OpenAPI instead of manually, will take some untangling and refactoring.
The text was updated successfully, but these errors were encountered:
Instead of turning everything around and converting to a design-first OpenAPI implementation, we could use swagger-core and throught it implement a code-first approach. I might take a look at how it works that way round.
The SolrWayback frontend is separated from the backend using well defined webservice endpoints. As these endpoints can also be used by other applications, such as dashboards of analysis tools ("notebooks"), they should be properly defined with description, sample arguments etc.
OpenAPI is the obvious choice and writing a proper YAML for the existing endpoints seems like a straight forward task. However, switching it around so that the webservice specific parts of the code base is generated by OpenAPI instead of manually, will take some untangling and refactoring.
The text was updated successfully, but these errors were encountered: