-
Bug
-
Resolution: Done
-
Normal
-
None
-
None
-
False
-
-
False
-
None
-
Unset
-
No
-
-
There are a couple of issues with the openapi API of daily digest preference.
1- GET /org-config/daily-digest/time-preference doesnt advertise a response on their openapi.
This leads to issues in the frontend validation, as the generated client is expecting nothing, but receiving something. The API is actually returning an string. We need to update the openapi (Probably missing some annotations)
2- PUT /org-config/daily-digest/time-preference does not return anything, but it doesn't tell what content-type is returning. The generated client assumes it is application/json, tries to decode the json and fails. We need to update this API to return a JSON (i.e. {success: true}) or change the content-type to text/plain.