fix: corregir deteccion de cambio de dia en zona horaria Colombia - #8
Merged
Conversation
- Detectar formato de entrada (fecha simple vs timestamp completo) - Evitar conversion incorrecta de fechas ya en formato local - Mantener conversion UTC a Colombia para timestamps - Agregar logging diferenciado para debugging - Garantizar generacion de nuevo cuadrado a las 00:00 Colombia Los commits ahora se asignan correctamente al dia local y el heatmap genera un nuevo cuadrado al cruzar la medianoche en Colombia (UTC-5). Resuelve #5
4 tasks
12 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Descripción
Este PR corrige el problema crítico donde el heatmap no generaba un nuevo cuadrado al pasar las 12:00 AM en Colombia (UTC-5). El método
adjustToBogotaDate()engithub-service.tsestaba aplicando incorrectamente una conversión de zona horaria a fechas que ya estaban en formato local, causando un desfase de un día en la visualización de commits.Cambios principales:
YYYY-MM-DDvs timestamp ISO 8601 completo)Soluciona el problema nº #5
Closes #5
Tipo de cambio
¿Cómo se ha probado esto?
Las pruebas se realizaron verificando los logs en el debugger de Stream Deck y validando el comportamiento del heatmap en tiempo real.
YYYY-MM-DDno sufren desfaseInstrucciones para reproducir:
npm run buildLista de verificación
Notas adicionales:
/^\d{4}-\d{2}-\d{2}$/