Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Authored measures' most-recent sort: mixed timezone offsets and same-instant ties still depend on order

Aperta
  • Qualcosa non va?
#750 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
data

Direzione di ricerca

Start with the review in #749 and trace the authored-measure sorting path, including normalize.ts and the cql-execution comparison behavior. Confirm how authored cms122 handles mixed offsets and same-instant ties, then get the owner’s decision on the tie rule before defining completion.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

backend bug

Two ordering edge cases are left after #749. Both affect only the authored measures; the official CMS measures don't use this sort.

1. Mixed timezone offsets order by text

cql-execution compares sort keys with <. A CQL DateTime has no valueOf, so it compares the toString() output, which ends in the offset. Results with the same offset sort correctly; results with different offsets can sort wrongly when they're close in time.

  • Example (authored cms122): 7.5% at 2026-05-13T23:00:00-10:00 (the newer result) against 10.5% at 2026-05-14T02:00:00+00:00 gives OVERDUE in both orders.
  • How it can happen: WebChart-sourced times carry a local offset (Maui is −10:00), while normalize.ts falls back to issued, usually in Z, when effectiveDateTime is missing.
  • Impact: at most one day on the day-window measures.
  • Fix options: normalise instants to UTC at ingest, or give the sort key one offset.

2. Ties keep input order

Two results at the same instant compare as "greater" both ways, so Last() picks the first-listed of the tied pair. That matters only for value-reading measures (authored cms122: 7.5 then 10.5 gives COMPLIANT; 10.5 then 7.5 gives OVERDUE). A tie needs a rule: a secondary key such as issued, or worst-value-wins. That choice is clinical, so it's an owner decision.

Found in #749's review. Low priority.

Lingua principale
TypeScript
Stelle
0
Fork
0
Merge medio
2h 51m
PR unite (30g)
109

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Taleef7/workwell

Tutte le issue di Taleef7/workwell

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.