deb-sig / deb-sig/double-entry-generator

enhancement: Better error messages

Open
#156 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Go
Stars
720
Forks
102
PR merge metrics
No merged PRs in 30d

Description

Our error message is not helpful now. For example:

[Provider-Alipay] 2025/04/15 11:06:51 get tx type error: 招银理财有限责任公司 [2023-09-14 CNY -1.12 1.23 朝朝宝转入 招银理财有限责任公司]
[Provider-Alipay] 2025/04/15 11:06:51 Failed to translate: Failed to translate bill: line 24: Failed to get the tx type 招银理财有限责任公司

It does not have enough info in the error message.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no file or test; start by reproducing the shown Alipay translation failure and locating the provider error path for the reported transaction at line 24. Done means the resulting error includes enough context to identify what failed and why.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.