No unit tests for four of six payment processors (nodeless, lnurl, opennode, zebedee)
维护者通常 1 天内回复
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 72/100
- Issue 类型
- 功能
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- typescript
调研方向
Read the four processor implementations in src/payments-processors/ and the existing specs for nwc and lnbits in test/unit/payments-processors/. Add unit specs covering createInvoice request mapping, getInvoice status mapping, and provider error or malformed response behavior. Done means all four processors have focused specs and the relevant unit tests pass.
由索引模型根据 Issue 内容生成。
描述
Gap
Four of the six payment processors have no unit tests at all — no spec file imports them:
src/payments-processors/nodeless-payments-processor.ts(74 lines)src/payments-processors/lnurl-payments-processor.ts(68 lines)src/payments-processors/opennode-payments-processor.ts(64 lines)src/payments-processors/zebedee-payments-processor.ts(61 lines)
Each implements getInvoice / createInvoice against a third-party API. The nwc and lnbits processors do have specs (test/unit/payments-processors/), and the zebedee/opennode/nodeless callback schemas are tested — so this is an inconsistency, not a project-wide absence. The money-moving code paths for four providers are the ones without coverage.
How measured
Import graph over the suite: 175 spec files vs 325 src/**/*.ts files — zero spec files reference these four modules.
What's worth covering
createInvoicerequest mapping per provider (amounts, units, metadata) — the shape bugs live heregetInvoicestatus mapping (paid/pending/expired) — misreading a provider's status is a funds bug- Error paths: provider outage, malformed responses — what the caller sees and whether anything is retried or lost
- 主要语言
- TypeScript
- 星标
- 829
- 派生
- 234
- 平均合并
- 17 小时 46 分钟
- 30 天内合并 PR
- 73
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
cameri/nostream 的其他 Issue
-
Website
难度 2/5 1-3 小时 新手友好度 84/100
维护者通常 1 天内回复
-
feat(payments): subscription lifecycle, renewal invoices and plan-based write access可能已有人在做 @Priyanshubhartistm 于 1 天前认领。 未关闭enhancement
cameri/nostream#908 · 已指派 1 人 ·
维护者通常 1 天内回复
-
Three repositories have no unit tests (notification-outbox, notification-delivery-log, nip05-verification)可能已有人在做 @Priyanshubhartistm 于 1 天前认领。 未关闭
难度 4/5 3-5 天 新手友好度 72/100
cameri/nostream#905 · 已指派 1 人 ·
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 72/100
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 25/100
维护者通常 1 天内回复
相似的 Issue
-
ready-for-agent
难度 2/5 1-3 小时 新手友好度 68/100
xavxyz/bei-shan-lin-shui#57 ·
维护者通常 1 天内回复
-
[BUG] rag: sentence content can cross the reported sentence boundaries可能已有人在做 @LJK-ikun 今天认领。 未关闭bug
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
-
bug needs-triage
难度 2/5 1-3 小时 新手友好度 70/100
维护者通常 1 天内回复
-
README: the Resource URI Schemas example's file://documents/* pattern only matches that literal URI未关闭
难度 1/5 1 小时以内 新手友好度 88/100
platformatic/mcp#361 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
siyuan-note/siyuan#20799 · 7 条评论 ·
维护者通常 1 天内回复