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

[BUG]: respect granularity when limiting analytics time-series buckets

Abierto Apto para principiantes
  • ¿Algo no está bien?
#333 3 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@Sparsh2105 ya está trabajando en esto.

Desde el 11/10/2026.

  • #334 de @Sparsh2105 — abierto

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
82/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
javascript
Área
analytics

Línea de trabajo

Lee src/services/analytics.js y las pruebas existentes en src/services/analytics.buildTimeSeries.test.js. Comprueba cómo buildTimeSeries gestiona los buckets semanales y mensuales, y cómo las pruebas verifican la cantidad y el orden de los buckets. El trabajo estará terminado cuando los resultados mensuales estén limitados a 12, los semanales a 26 y los resultados sigan ordenados cronológicamente.

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

Descripción

bug
Bug Description

The buildTimeSeries function in src/services/analytics.js limits its output to the last 12 buckets regardless of the selected granularity.

As a result, the Weekly view displays only approximately 12 weeks of activity (~3 months), while the Monthly view can display up to 12 months of activity. This creates inconsistent historical windows when switching between granularities.

The function already accepts a granularity parameter, but the final .slice(-12) applies the same limit to both monthly and weekly buckets.

Expected Behavior:

  • Monthly granularity should retain up to 12 buckets (~12 months).
  • Weekly granularity should retain up to 26 buckets (~6 months).

Actual Behavior:

Both granularities are limited to 12 buckets, causing older activity to disappear from the Weekly view.

Proposed Fix

Use a bucket limit based on the selected granularity instead of hardcoding the limit to 12:

const SLICE_COUNT = granularity === 'weekly' ? 26 : 12;

return Object.values(buckets)
  .sort((a, b) => a.date.localeCompare(b.date))
  .slice(-SLICE_COUNT);

This allows the Weekly view to retain up to 26 buckets while preserving the existing 12-bucket limit for the Monthly view.

Testing

Update src/services/analytics.buildTimeSeries.test.js to verify that:

  • Monthly granularity returns at most 12 buckets.
  • Weekly granularity returns at most 26 buckets.
  • Weekly granularity can return more than 12 buckets when sufficient data is available.
  • Results remain sorted chronologically.
Scope
  • Implementation: src/services/analytics.js
  • Tests: src/services/analytics.buildTimeSeries.test.js
  • No UI, layout, or API changes are required.
Steps to Reproduce
  1. Run the application locally using npm run dev.
  2. Explore an organisation with sufficient issue or pull request history, such as AOSSIE-Org.
  3. Navigate to the Analytics page.
  4. Click Run Complete Analysis to populate the time-series chart.
  5. Select Monthly granularity and observe the displayed date range.
  6. Switch to Weekly granularity.
  7. Observe that the chart displays at most 12 weekly buckets, even when older activity is available.

The issue can also be reproduced by passing more than 12 distinct weekly buckets to buildTimeSeries in src/services/analytics.js.

Logs and Screenshots

No error logs are expected because this is a data truncation issue rather than a runtime error.

A screenshot comparing the Monthly and Weekly analytics views would help demonstrate the inconsistent historical windows.

Relevant implementation: src/services/analytics.js, where the returned buckets are limited using .slice(-12).

Relevant tests: src/services/analytics.buildTimeSeries.test.js.

Environment Details
  • OS: Ubuntu 26 LTS
  • Browser: Brave (Chromium-based)
  • Runtime: Node.js 22.22.1
  • Project: AOSSIE-Org/OrgExplorer
  • Setup: Local development environment using npm run dev
  • Additional context: The issue concerns the time-series bucket limit in src/services/analytics.js.
Impact

Medium - Feature works but has issues

Code of Conduct
  • I have joined the Discord server and will post updates there
  • I have searched existing issues to avoid duplicates
Lenguaje dominante
JavaScript
Estrellas
44
Forks
133
Merge medio
2 d 22 h
PR fusionados (30 d)
10

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 AOSSIE-Org/OrgExplorer

Todos los issues de AOSSIE-Org/OrgExplorer

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.