I8.10 · Watch Ably

未關閉
#60 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
35/100
Issue 類型
功能
描述清晰度
描述清楚
活躍度
活躍
技術堆疊
go, openapi

研究方向

Start by reading the parent issue and the repository’s CONTRIBUTING.md and provider template. Verify Ably’s official deprecation, changelog, API specification, and SDK sources, recording URLs and check dates; then inspect existing provider catalog entries and golden tests to follow their patterns. Done means the sources and formats are cataloged, replay fixtures produce expected events, the provider page and docs index are updated, and client fix requirements are recorded.

由索引模型根據 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 Ably, I want patch-it to know when Ably breaks, deprecates or retires something, so I get the fix before production does.

Subtasks

  • Find Ably'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/ably.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 Ably 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 摘要。