Inbox: rolling "Last 3 days" option in the Updated filter

Abierto
  • ¿Algo no está bien?
#3,301 1 comentario 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
3/5
Tiempo estimado
Medio día
Aptitud para principiantes
45/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
frontend

Línea de trabajo

The payload names no files, so start by finding the Updated date filter in the Inbox UI and where its presets (Today, Last 7 days, Last 30 days) are defined and persisted. Check how the existing presets compute their cutoff and how the selection is stored. Done when a rolling 'Last 3 days' option appears, filters threads by their last update, and is remembered like the other presets. The issue leaves open whether to add a preset or make Custom range relative, so confirm the choice with the maintainers first.

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

Descripción

Problem

The Updated filter has Today, Last 7 days, Last 30 days and Custom range. I want to see only threads that moved in the last few days (for example 3). Today is too narrow and Last 7 days is too wide. Custom range takes two fixed dates, so it doesn't move forward with time and I'd have to pick the dates again every day.

Current behavior (0.28.63)

Filter → Updated: Today, Last 7 days, Last 30 days, Custom range… (From/To date inputs).

Request

  1. A rolling preset such as Last 3 days (or Last 24 hours / Last 3 days), remembered like the other presets.
  2. Or let Custom range take a relative value ("last N days") that stays relative.

Why

Many threads finish within a few days. With a rolling "last 3 days" view, quiet threads drop out of my list by themselves, so neither I nor my agents need to archive them by hand just to keep the list readable.

Lenguaje dominante
TypeScript
Estrellas
8.7k
Forks
649
Merge medio
10 h 45 min
PR fusionados (30 d)
830

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 backnotprop/plannotator

Todos los issues de backnotprop/plannotator

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.