Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Live search: ask the whole mailbox and connected platforms, not only what Taskuary has read

Abierto
  • ¿Algo no está bien?
#261 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
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github, python, react
Área
backend, full-stack, search

Línea de trabajo

Start with taskuary/search.py and website/src/SearchEverything.jsx to understand the existing local search flow; then read the Graph $search example in taskuary/senders.py and IMAP search in taskuary/chains.py. The issue also points to the Teams, Slack, GitHub, and SharePoint connector clients and their search APIs. Done means users can choose Live search across connected sources, open or pull in results, and use it from Assistant chat while respecting connection scope.

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

Descripción

What

Search today covers only what Taskuary has already ingested (taskuary/search.py). Add a live search that asks the sources themselves - the whole mailbox history and the connected platforms (Teams, Slack, GitHub, SharePoint, ...) - so "what did we agree with the vendor last spring?" finds mail from before Taskuary started reading.

Proposed interaction

In the search box, a choice between In Taskuary (today's local index, instant) and Live (asks each connected source). Live results are marked with their source, can be opened, and can be pulled in as a task or attached to one. The Assistant chat can use the same live search to answer questions about the whole mailbox.

Why

Superhuman (Ask AI), Copilot in Outlook and Gemini in Gmail all answer over the whole mailbox; Taskuary only searches its window.

What exists to build on

  • taskuary/search.py (one search, totals by type, caps) and website/src/SearchEverything.jsx.
  • A narrow Graph $search already in taskuary/senders.py and an IMAP search in taskuary/chains.py.
  • Connector clients for Teams, Slack, GitHub, SharePoint (their own search APIs).

Notes

  • Read-only; respects each connection's scope.
  • Results from a live search are not stored unless the owner pulls one in.
  • Use invented data in tests (northwind.example).
Lenguaje dominante
Python
Estrellas
116
Forks
22
Merge medio
8 h 45 min
PR fusionados (30 d)
41

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.