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 }}
Repository navigation
Refactoring envelope of successful responses and its client contract #256
Revisit the envelope of successful (HTTP 200) responses from the stats lambda. Every success body currently contains two fields that duplicate the HTTP response:
success: true is already implied by the 2xx status code.
statusCode is repeated in the body, although it is already the API Gateway statusCode.
This is built in src/utils/utils.py (success response builders for data/pagination and aggregations).
Background
Raised by @lsulak in review of PR #243: "success is quite visible from the status code, and then also status code is there twice. Is there any situation when it differentiates?"
Activity