improve Typesense client exception semantics

[runeanielsen]

Note

Breaking changes!

This update will result in breaking changes for clients that used null checks to see if a resource existed or not. The new implementation will throw an TypesenseApiNotFoundException instead, the benefit is that the API will be more uniform overall.

Change

Now provides a range of more specific exceptions. The reason is to improve error-handling. Instead of only having TypesenseApiException, the client now has a range of exception types all inheriting from TypesenseApiException, so if you're already catching TypesenseApiException, you won't have to change anything. The error types has been taken from Typesense documentation regarding API errors link.

Type	Description
TypesenseApiException	Base exception type for Typesense api exceptions.
TypesenseApiBadRequestException	Bad Request - The request could not be understood due to malformed syntax.
TypesenseApiUnauthorizedException	Unauthorized - Your API key is wrong.
TypesenseApiNotFoundException	Not Found - The requested resource is not found.
TypesenseApiConflictException	Conflict - When a resource already exists.
TypesenseApiUnprocessableEntityException	Unprocessable Entity - Request is well-formed, but cannot be processed.
TypesenseApiServiceUnavailableException	Service Unavailable - We’re temporarily offline. Please try again later.