Skip to content

Commit 95e4749

Browse files
committed
Refactor: Rename volley error msg to plain error msg for app log e func
There is no point to hold a reference to 'volley' anyway in the project and this way to make the implementation to seem to be binding to a specific networking framework, which it isn't.
1 parent 709f7a4 commit 95e4749

File tree

1 file changed

+5
-5
lines changed
  • WordPressUtils/src/main/java/org/wordpress/android/util

1 file changed

+5
-5
lines changed

WordPressUtils/src/main/java/org/wordpress/android/util/AppLog.java

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -205,18 +205,18 @@ public static void e(T tag, Throwable tr) {
205205
* Sends a ERROR log message
206206
* @param tag Used to identify the source of a log message. It usually identifies the class or activity where the
207207
* log call occurs.
208-
* @param volleyErrorMsg
208+
* @param errorMsg
209209
* @param statusCode
210210
*/
211-
public static void e(T tag, String volleyErrorMsg, int statusCode) {
212-
if (TextUtils.isEmpty(volleyErrorMsg)) {
211+
public static void e(T tag, String errorMsg, int statusCode) {
212+
if (TextUtils.isEmpty(errorMsg)) {
213213
return;
214214
}
215215
String logText;
216216
if (statusCode == -1) {
217-
logText = volleyErrorMsg;
217+
logText = errorMsg;
218218
} else {
219-
logText = volleyErrorMsg + ", status " + statusCode;
219+
logText = errorMsg + ", status " + statusCode;
220220
}
221221
Log.e(TAG + "-" + tag.toString(), logText);
222222
addEntry(tag, LogLevel.w, logText);

0 commit comments

Comments
 (0)