Conversion breakdowns drop every later day once the series limit is reached

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

Los mantenedores suelen responder en 1 día

@officialasishkumar ya está trabajando en esto.

Desde el 7/11/2026.

  • #658 de @officialasishkumar — abierto

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Estancado
Stack tecnológico
typescript
Área
data-visualization

Línea de trabajo

Start with packages/core/src/modules/chart/conversion.service.ts and inspect toSeries where the limit is checked before the breakdown key. Compare its behavior with funnel.service.ts, whose equivalent fix is described in the issue. Done means the limit caps the number of breakdown series while every kept series retains all days in the range; pull request #658 is already open.

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

Descripción

Description

A conversion chart with a breakdown loses data once the number of breakdown values reaches the report's limit. Every row after that point is dropped, including the later days of the series that were kept. Those lines stop early, and if the limit is reached on the first day, each series shows only that day. The summary and table built from the series are wrong in the same way.

The report editor sends limit: 500, so this happens with any breakdown that has at least 500 values over the range (paths, referrers, many custom properties). A smaller limit makes it happen sooner.

Root cause

toSeries in packages/core/src/modules/chart/conversion.service.ts checks the limit before it looks at the row's breakdown key:

if (limit && Object.keys(acc).length >= limit) {
  return acc;
}

The query orders rows by event_day, then by breakdown, so once the limit is reached, every later row is discarded, including rows of series that were already accepted.

The funnel's toSeries (funnel.service.ts) had the same bug and was fixed by checking the limit only for new keys. The conversion version never got that fix.

Expected behavior

The limit caps how many breakdown series come back. The series that are kept still have every day in the range.

Lenguaje dominante
TypeScript
Estrellas
7.3k
Forks
539
Merge medio
1 d 20 h
PR fusionados (30 d)
80

Preparar el entorno

  • Incluye un Dockerfile o un archivo de Docker Compose
  • Sin plantilla de pull request
  • Sin guía de contribución

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 Openpanel-dev/openpanel

Todos los issues de Openpanel-dev/openpanel

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.