From 945ce808403c095b17e25fb2741d52ac04a02dba Mon Sep 17 00:00:00 2001 From: Sylvain Briat Date: Wed, 3 Apr 2024 13:39:09 +0200 Subject: [PATCH] improve documentation --- README.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/README.md b/README.md index 091c3c3..0191775 100644 --- a/README.md +++ b/README.md @@ -167,6 +167,7 @@ The app exposes the following [gRPC](https://grpc.io/) services : - **seatsProposed** (integer, optional): number of seats proposed as driver (_default : 3_) - **seatsRequested** (integer, optional): number of seats requested as passenger (_default : 1_) - **waypoints**: an array of addresses that represent the waypoints of the journey (only first and last waypoints are used for passenger ads). Note that positions are **required** and **must** be consecutives + - **excludedAdId** (optional): the id of an ad to be excluded from the results (useful to avoid self-matchings) - **algorithmType** (optional): the type of algorithm to use (as of 2023-09-28, only the default `PASSENGER_ORIENTED` is accepted) - **remoteness** (integer, optional): an integer to indicate the maximum flying distance (in metres) between the driver route and the passenger pick-up / drop-off points (_default : 15000_) - **useProportion** (boolean, optional): a boolean to indicate if the matching algorithm will compare the distance of the passenger route against the distance of the driver route (_default : 1_). Works in combination with **proportion** parameter @@ -218,10 +219,6 @@ If the matching is successful, you will get a result, containing : Matching is a time-consuming process, so the results of a matching request are stored in cache before being paginated and returned to the requester. An id is attributed to the overall results of a request : on further requests (for example to query for different pages of results), the requester can provide this id and get in return the cached data, avoiding another longer process of computing the results from scratch. Obviously, new computing must be done periodically to get fresh new results ! -There's also a basic cache to store the results of the _same_ request sent multiple times successively. - -Cache TTLs are customizable in the `.env` file. - ## Tests / ESLint / Prettier Tests are run outside the container for ease of use (switching between different environments inside containers using prisma is complicated and error prone).