[Feature Request]: Add `chat.bsky.convo` reply and group conversation support

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

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
43/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
冷清
技术栈
swift
领域
api

调研方向

Start with Sources/ATProtoKit/Models/Lexicons/chat.bsky/Convo/ChatBskyConvoDefs.swift and the wrappers under Sources/ATProtoKit/APIReference/ChatBskyAPI/; compare their existing acceptConvo and muteConvo patterns with the referenced chat.bsky.convo lexicons. Add the listed reply and group types and fields, then expose the four requested endpoints with api.bsky.chat routing. Done when replies, group metadata, and all four operations are available through ATProtoBlueskyChat.

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

描述

new feature
Summary

chat.bsky.convo upstream has been extended with two cross-cutting additions that are not yet reflected in the typed models or wrappers: message-level reply (replyTo on both input and view) and group conversations (convoView.kind union with #groupConvo, plus four new XRPC endpoints). Currently the SDK exposes neither, so the entire reply / group surface is unreachable through ATProtoBlueskyChat.

Pain points

The reply / group definitions are absent from the typed models and wrappers, so the whole surface is unreachable through ATProtoBlueskyChat: typed quote-reply on sendMessage is impossible, an incoming reply's parent is silently dropped on decode (no field-level .unknown fallback), a group is indistinguishable from a 1:1 DM with its metadata unreachable, and the group / lock endpoints require raw XRPC that re-implements the api.bsky.chat host routing / auth ATProtoBlueskyChat already provides. See Additional Context for the specific undefined types, fields, and wrappers.

Considered Alternatives

Raw XRPC for the entire chat surface (loses typed pipeline and the isRelatedToBskyChat host routing) — only viable per-client and brittle.

Is this a breaking change?

No

Library Examples

N/A

Additional Context
Missing types
Lexicon Suggested type
chat.bsky.convo.defs#replyRef ReplyReferenceDefinition — messageID: String (messageId)
chat.bsky.convo.defs#messageBeforeUserJoinedGroupView MessageBeforeUserJoinedGroupViewDefinition — per lexicon
chat.bsky.convo.defs#groupConvo GroupConvoDefinition — name: String?, createdAt: Date, lockStatus: String, lockStatusModerationOverride: String?, memberCount: Int, memberLimit: Int, joinLink: String?, joinRequestCount: Int, unreadJoinRequestCount: Int
Missing fields on existing types
Lexicon Suggested field
chat.bsky.convo.defs#messageInput replyTo: ReplyReferenceDefinition?
chat.bsky.convo.defs#messageView replyTo: ReplyToUnion? (messageView | deletedMessageView | messageBeforeUserJoinedGroupView)
chat.bsky.convo.defs#convoView kind: KindUnion? (groupConvo)
Missing wrappers
Lexicon Suggested method
chat.bsky.convo.getConvoMembers getConversationMembers(from:limit:cursor:)
chat.bsky.convo.listConvoRequests listConversationRequests(limit:cursor:)
chat.bsky.convo.lockConvo lockConversation(by:)
chat.bsky.convo.unlockConvo unlockConversation(by:)

All four sit on api.bsky.chat, mirror the existing acceptConvo / muteConvo shape, and require isRelatedToBskyChat: true routing.

References
主要语言
Swift
星标
226
派生
40
平均合并
5 小时 8 分钟
30 天内合并 PR
3

环境准备

从这里开始

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

MasterJ93/ATProtoKit 的其他 Issue

查看 MasterJ93/ATProtoKit 的全部 Issue

相似的 Issue

更多 Swift Issue

把新 issue 发到你的邮箱

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