I7.4 · Watch WorkOS
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 5/5
- 預估耗時
- 一週以上
- 新手友好度
- 34/100
- Issue 類型
- 功能
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- go
研究方向
Start with the parent issue and the repository’s provider template, catalog format, existing provider implementations, tests, and CONTRIBUTING.md; identify and verify WorkOS’s official sources and record when each was checked. Build the provider around those sources, add saved-source tests and a historical breaking-change replay fixture, then document it in providers/workos.md and docs/plugins.md. Done means daily ingest emits events with source_url and exact source_excerpt, the replay produces the expected events, and the page dates every source check.
由索引模型根據 Issue 內容生成。
描述
Part of https://github.com/patch-it-dev/patch-it-plugins/issues/10
Story
As a developer whose code calls WorkOS, I want patch-it to know when WorkOS breaks, deprecates or retires something, so I get the fix before production does.
Subtasks
- Find WorkOS'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/workos.mdfrom the template - Add or update its row in
docs/plugins.md(seeCONTRIBUTING.md) - Note what the client needs to fix it (existing handler, or a new fix kind in the client)
Acceptance criteria
- Daily ingest emits WorkOS events, each with
source_urland an exactsource_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
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
patch-it-dev/patch-it-plugins 的其他 Issue
-
story
難度 2/5 1-3 小時 新手友好度 78/100
patch-it-dev/patch-it-plugins#120 ·
維護者通常 1 天內回覆
-
story
難度 5/5 一週以上 新手友好度 35/100
patch-it-dev/patch-it-plugins#119 ·
維護者通常 1 天內回覆
-
story
難度 4/5 3-5 天 新手友好度 35/100
patch-it-dev/patch-it-plugins#115 · 1 則留言 ·
維護者通常 1 天內回覆
-
good first issue story
難度 5/5 一週以上 新手友好度 25/100
patch-it-dev/patch-it-plugins#104 ·
維護者通常 1 天內回覆
-
good first issue story
難度 5/5 一週以上 新手友好度 35/100
patch-it-dev/patch-it-plugins#103 ·
維護者通常 1 天內回覆
查看 patch-it-dev/patch-it-plugins 的全部 Issue
相似的 Issue
-
bug
難度 1/5 1 小時以內 新手友好度 88/100
orion-belt-dev/orion-belt#181 ·
維護者通常 1 天內回覆
-
documentation good first issue
難度 2/5 1-3 小時 新手友好度 79/100
kubesmarts/logic-operator#105 ·
維護者通常 1 天內回覆
-
難度 1/5 1-3 小時 新手友好度 78/100
jakartaee/jakartablogs.ee#125 ·
-
難度 2/5 1-3 小時 新手友好度 72/100
MUKE-coder/grit#228 ·
-
enhancement good first issue
難度 2/5 1-3 小時 新手友好度 88/100