I8.3 · Watch Resend

未关闭
#53 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
38/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
go, javascript, openapi, python

调研方向

Start with the plugin catalog conventions in CONTRIBUTING.md and the provider page template; then identify Resend’s official deprecation, API, OpenAPI, and SDK release sources, recording each checked date. Build source fixtures and golden tests, including one historical breaking change replay, and document the required client fix. Done means daily ingest emits events with exact source URLs and excerpts, and providers/resend.md lists every verified source.

由索引模型根据 Issue 内容生成。

描述

good first issue story

Part of https://github.com/patch-it-dev/patch-it-plugins/issues/11

Story

As a developer whose code calls Resend, I want patch-it to know when Resend breaks, deprecates or retires something, so I get the fix before production does.

Subtasks

  • Find Resend's sources and record them with the date checked (verify, don't guess; leave TBD if unknown):
    • deprecations / sunset page
    • API changelog (RSS / Atom if there is one)
    • OpenAPI spec, if published
    • official SDKs and their release notes / changelogs (Python and JS first)
    • API versioning scheme (date-based, path, header, none)
  • Pick the format plugin for each source (OpenAPI, RSS, GitHub Releases, changelog file, registry, prose) and add catalog lines
  • Golden test: a saved copy of each source in, the expected events out
  • One real historical breaking change as a replay fixture
  • Provider page providers/resend.md from the template
  • Add or update its row in docs/plugins.md (see CONTRIBUTING.md)
  • Note what the client needs to fix it (existing handler, or a new fix kind in the client)

Acceptance criteria

  • Daily ingest emits Resend events, each with source_url and an exact source_excerpt
  • The replayed historical change produces the right events
  • The provider page lists every source with its date checked
主要语言
Go
星标
0
派生
0
平均合并
2 小时 59 分钟
30 天内合并 PR
17

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

patch-it-dev/patch-it-plugins 的其他 Issue

查看 patch-it-dev/patch-it-plugins 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。