[mastodon-client] Log note lookup failures with logger instead of console

This commit is contained in:
Laura Hausmann 2023-10-11 19:55:26 +02:00
parent 1fdea9866a
commit 695528bed7
No known key found for this signature in database
GPG key ID: D044E84C5BE01605

View file

@ -21,7 +21,7 @@ import { resolveUser } from "@/remote/resolve-user.js";
import { createNote } from "@/remote/activitypub/models/note.js";
import { getUser } from "@/server/api/common/getters.js";
import config from "@/config/index.js";
import { MastoContext } from "@/server/api/mastodon/index.js";
import { logger, MastoContext } from "@/server/api/mastodon/index.js";
export class SearchHelpers {
public static async search(q: string | undefined, type: string | undefined, resolve: boolean = false, following: boolean = false, accountId: string | undefined, excludeUnreviewed: boolean = false, maxId: string | undefined, minId: string | undefined, limit: number = 20, offset: number | undefined, ctx: MastoContext): Promise<MastodonEntity.Search> {
@ -139,7 +139,7 @@ export class SearchHelpers {
return isPost(object) ? createNote(getApId(object), resolver.reset(), true).then(p => p ? [p] : []) : [];
}
} catch (e: any) {
console.log(`[mastodon-client] resolve note '${q}' failed: ${e.message}`);
logger.warn(`Resolving note '${q}' failed: ${e.message}`);
return [];
}
}