[Feat] 在所有出错的地方打印error日志

Repository metrics

Stars

2,651 stars (2,651 stars)

PR merge metrics

PR metrics pending (PR metrics pending)

Description

if err != nil {
	ctx.SendChain(message.Text("ERROR: ", err))
	return
}

if err != nil {
	log.Error("<插件名称>",err)
        ctx.SendChain(message.Text("ERROR: ", err))
	return
}

Contributor guide

Research direction

Add log.Error statements in all plugin error handling blocks where errors are sent via ctx.SendChain. Search for patterns like 'if err != nil { ctx.SendChain(message.Text("ERROR: ", err)); return }' and add a log.Error call before the send.

Tech stack

go

Domain

backend

Issue type

Feature

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

2

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-3 hours

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

Active

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

Clear

Prerequisites

GoGit

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

75