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
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -142,7 +142,7 @@ Changes from 1.0.3 -> 2.0.0 are listed below
142
142
- This affects any development that uses the `message` or `isSuccessful` from response object of APIs that is Result object.
143
143
144
144
**How should I update my code?**
145
-
- If you still need to use `message` it will be there in the custom exception and could be raised `isSuccessful` properties in your own code from status code with `httpStatusCode` that is coming in the responseMetaData with `getResponseMetaData()` of response object or custom exception.
145
+
- If you still need to use `message` it will be there in the custom exceptions that could be raised when calling the various API methods. `isSuccessful` can be derived to be `true` if the API method doesn't throw any exception.
If the upload is successful, result will be there as an object of `Result` class that contains the same all the parameters received from ImageKit's servers.
413
413
414
-
If the upload fails, custom exception getting thrown and by doinf`getMessage()`will contain the same error message received from ImageKit's servers.
414
+
If the upload fails, custom exception is thrown and `getMessage()`can be called to get the error message received from ImageKit's servers.
0 commit comments