Hacktoberfest 2026：維護者為十月標記出來的 issue，仍然開放、適合新手。 瀏覽 Hacktoberfest issue

feat(payments): subscription data model and plan settings

未關閉
  • 哪裡不對？
#848 0 則留言 0 個 reaction 已指派 1 人 在 GitHub 檢視

維護者通常 1 天內回覆

@Priyanshubhartistm 已經在處理了。

開始於 2026年10月16日。

  • #849 來自 @Priyanshubhartistm —— 未關閉

評估

這個 Issue 還沒有評估資料。

描述

enhancement

Is your feature request related to a problem? Please describe.
Admission is a one-time boolean (users.is_admitted). There is nowhere to record a paid period, a plan, or when access ends, so recurring billing and tiered access (#673) cannot be built. This is the first, behaviour-neutral step.

Describe the solution you'd like

  • A user_subscriptions table (pubkey, plan id, status, period start/end, grace end, cancel-at-period-end) and the invoices columns plan_id, period_start, period_end, via a migration. A subscription is keyed by pubkey, so no separate subscription id is needed.
  • payments.subscriptionPlans[] in settings (id, price, interval, grace period, per-plan limits), with types, defaults (empty list), validation in validateSettings, and CONFIGURATION.md docs.
  • IUserSubscriptionRepository (find by pubkey, upsert, list due for renewal/expiry) and the invoice repository/Invoice type changes, with unit tests.
  • The migration grandfathers every existing is_admitted user onto a non-expiring plan so enabling plans later never locks anyone out.
  • No change to runtime behaviour: with no plans configured the relay behaves exactly as today.

Additional context

  • Design: #673. Earlier groundwork for the same layer.
主要語言
TypeScript
星號
829
分支
234
平均合併
22 小時 43 分鐘
30 天內合併 PR
52

環境準備

從這裡開始

  1. 先讀完整個 Issue，再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫，在一個分支上完成修改。
  4. 送出 Pull Request，並在描述裡引用這個 Issue 編號。

cameri/nostream 的其他 Issue

查看 cameri/nostream 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。