Slack: reply to a Slack message from Taskuary

Abierto
  • ¿Algo no está bien?
#262 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
fastapi, python
Área
api, backend

Línea de trabajo

Start with taskuary/outbound.py and trace how existing email, Teams, and WhatsApp replies enter the approval queue and report delivery failures. Then inspect the Slack card polling and sign-in paths to identify how each card retains its conversation and scopes. Add tests with a fake Slack client and invented workspaces; done means an approved reply posts in the owning card's thread and missing chat:write scope follows the existing fix path.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

What

Slack messages come into Taskuary (each Slack card is polled), but there is no way to answer one from Taskuary: no draft, no Send through Slack. Replies exist for email, Teams, WhatsApp and other channels.

Sketch

  • A reply on a Slack-sourced task drafts into the usual approval queue (Review / Close out) and, on the owner's Send, posts in the same thread (chat.postMessage with thread_ts) through the card the message came in on.
  • Delivery state and failures follow the existing outbound pattern (taskuary/outbound.py), so the card shows a failed send in plain words with its fix.
  • Respect the card's scopes (needs chat:write); a token without it shows the existing sign-in/fix path.

Notes

  • Several Slack cards are already polled per card; the reply should leave through the card that owns the conversation.
  • Tests with a fake Slack client and invented workspaces (northwind.example).
Lenguaje dominante
Python
Estrellas
116
Forks
22
Merge medio
5 h 6 min
PR fusionados (30 d)
23

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de ldbumble/taskuary

Todos los issues de ldbumble/taskuary

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.