[Feature Request]: Add `chat.bsky.convo` reply and group conversation support
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 43/100
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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
- Lexicon root: https://github.com/bluesky-social/atproto/tree/main/lexicons/chat/bsky/convo
defs.json: https://github.com/bluesky-social/atproto/blob/main/lexicons/chat/bsky/convo/defs.json- Affected file:
Sources/ATProtoKit/Models/Lexicons/chat.bsky/Convo/ChatBskyConvoDefs.swift - Affected wrapper namespace:
Sources/ATProtoKit/APIReference/ChatBskyAPI/
- Lenguaje dominante
- Swift
- Estrellas
- 226
- Forks
- 40
- Merge medio
- 5 h 8 min
- PR fusionados (30 d)
- 3
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de MasterJ93/ATProtoKit
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
MasterJ93/ATProtoKit#344 ·
-
enhancement
Dificultad 4/5 1-2 días Aptitud para principiantes 52/100
MasterJ93/ATProtoKit#337 · 3 comentarios ·
-
new feature
Dificultad 4/5 3-5 días Aptitud para principiantes 52/100
MasterJ93/ATProtoKit#321 · 1 comentario ·
-
new feature
Dificultad 4/5 1-2 días Aptitud para principiantes 55/100
MasterJ93/ATProtoKit#316 · 1 comentario ·
-
new feature
Dificultad 2/5 1-3 horas Aptitud para principiantes 35/100
MasterJ93/ATProtoKit#216 · 1 comentario ·
Todos los issues de MasterJ93/ATProtoKit
Issues similares
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 67/100
Los mantenedores suelen responder en 1 día
-
🎉 Add WoundAbierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 77/100
jaywcjlove/awesome-mac#4357 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
-
Bug: on hover a tab's name in Cra stops ~16 pt short of Arc's, with 24 pt of air before the ✕Abiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
VictorKildahl/cra#243 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 83/100
OneBusAway/vehicle-positions#260 ·
Los mantenedores suelen responder en 1 día