From d03aa7f1f358a2db69df3d0ff3bb6e5eb9c4e737 Mon Sep 17 00:00:00 2001
From: Ludovic Robert <30499179+bigludo7@users.noreply.github.com>
Date: Tue, 1 Oct 2024 16:03:19 +0200
Subject: [PATCH] Update location-retrieval.yaml

Fixing linting + adding precision as suggested by @alpaycetin74:
`Note: if both `maxAge` and `maxSurface` requirements fail, the system can either send back one or the other error code.  `
---
 code/API_definitions/location-retrieval.yaml | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/code/API_definitions/location-retrieval.yaml b/code/API_definitions/location-retrieval.yaml
index 5e5a783..109d844 100644
--- a/code/API_definitions/location-retrieval.yaml
+++ b/code/API_definitions/location-retrieval.yaml
@@ -46,8 +46,9 @@ info:
 
     * **Max Surface**: Maximum surface in square meters which is accepted by the client for the location retrieval.
 
-      * absence of `maxSurface` means that "any surface size" is acceptable for the client. 
+      * absence of `maxSurface` means that "any surface size" is acceptable for the client.
       * If the system is not able to provide an area with a surface acceptable with the client request, an error 422 with code LOCATION_RETRIEVAL.UNABLE_TO_FULFILL_MAX_SURFACE is sent back.
+      * Note: if both `maxAge` and `maxSurface` requirements fail, the system can either send back one or the other error code.  
 
 
     # API Functionality