Skip to content

chart=2.110.27,image=2.110.27

chart=2.110.27,image=2.110.27: Document more error responses in Swagger (#1657)
@pcapriotti pcapriotti tagged this 27 Jul 09:27 
* Introduce notConnected ErrorDescription

Also, align dynamic errors with static error description, by using a
function to convert an `ErrorDescription` value to a `Wai.Error`.

* Add CanThrow annotation for servant endpoints

* Add note about lack of static guarantees

* Add ErrorDescription for operationDenied

* Use a more realistic UUID example in Swagger

* Better example for ErrorDescription in Swagger

* Inline ErrorDescription schema in Swagger

* Make label of ErrorDescription static

* Make label field of ErrorDescription an enum

Also add values to the enum when multiple ErrorDescription types have
the same status code.

* Convert notATeamMember error to ErrorDescription

* Convert actionDenied error to ErrorDescription

* Make status code of ErrorDescription an enum

* schema-profunctor: Fix type of swagger enum

* Convert codeNotFound error to ErrorDescription

* Convert convAccessDenied error to ErrorDescription

* Update CHANGELOG

* Integrate ErrorDescription with MultiVerb

* Convert some Brig errors to ErrorDescription

* Convert EmptyErrorForLegacyReasons to MultiVerb

* Convert tooManyClient error to ErrorDescription

* Convert missingAuth error to ErrorDescription

* Convert malformedPrekey errors to ErrorDescription

* Test empty error content type

* Follow changes in MultiVerb

* Convert UpdateResult to MultiVerb

* Convert userNotFound error to ErrorDescription
Assets 2
Loading