Wendy's purpose is to give the ability to create, manage, and sync pending API tasks for a user. Right now, the library also adds the ability to perform API calls to download/upload/request network calls.
That functionality should be taken out of the library and put into another library. Think of it like Retrofit and OkHttp.
Also, with the networking API library, create modules so that user can parse JSON data and deserialize it into objects. override fun apiResponseError(statusCode: Int, response: Response<Any>, headers: Headers, errorVo: Class<out ErrorResponseVo>): Throwable? { in WendyProcessApiResponse is an example of a bad API. I am requiring the user deserializes the response.errorBody() with errorVo. The library should do this.
I have removed this need with the newest version of Wendy which I will update the code for shortly. There is no networking at all. All networking (if any) is done via the end dev user.
Wendy's purpose is to give the ability to create, manage, and sync pending API tasks for a user. Right now, the library also adds the ability to perform API calls to download/upload/request network calls.
That functionality should be taken out of the library and put into another library. Think of it like Retrofit and OkHttp.
Also, with the networking API library, create modules so that user can parse JSON data and deserialize it into objects.
override fun apiResponseError(statusCode: Int, response: Response<Any>, headers: Headers, errorVo: Class<out ErrorResponseVo>): Throwable? {
inWendyProcessApiResponse
is an example of a bad API. I am requiring the user deserializes theresponse.errorBody()
witherrorVo
. The library should do this.