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
{{ message }}
This repository has been archived by the owner on May 6, 2021. It is now read-only.
Currently, the REST API is defined and served by httprouter. We should switch to Goa to design and serve the API. Partly because it aligns with the other services and partly since this allows for automatic client generation on the caller side of the Idler (aka Proxy).
The text was updated successfully, but these errors were encountered:
No, there are several things here. One issue (this one) is about using Goa to define the REST API for the Idler itself. It's own API. #105 is about using Goa's ability to generate a client from a given Goa spec file. I would consider this issue to be the more important one.
hferentschik
changed the title
Use Goa for defining the REST API
Use Goa for defining the Idler REST API
Feb 27, 2018
Currently, the REST API is defined and served by httprouter. We should switch to Goa to design and serve the API. Partly because it aligns with the other services and partly since this allows for automatic client generation on the caller side of the Idler (aka Proxy).
The text was updated successfully, but these errors were encountered: