clients

Value Members

1. object BrewdogApiContract extends Contract

   

2. object BrewdogApiHttp

   

3. object ClientSideAndSharedRouteSpecExample extends App

   

   Simple example of how to define client endpoints using the same techniques as the server routes.

   Simple example of how to define client endpoints using the same techniques as the server routes. Note that the client will automatically reject (with a 400) any unknown or missing parameters, as per the specified route. The response is also decorated with the anonymised route, allowing for collection of metrics about timing and number of requests going to the downsteam systems.

   This example also shows how you can re-use the RouteSpec across client and servers, thus allowing really simple stub/fake implementations of remote systems to be created.

4. object ContractProxyExample extends App

   

   This example shows how to use a contract to provide a Swagger-documented Proxy API for a set of remote routes.