mirror of
https://github.com/4gray/iptvnator.git
synced 2026-10-08 17:06:15 -08:00
4gray
5b091809ef
## Summary - Normalize Xtream recently-added timestamps across UI, import, and dashboard query paths. - Filter future/invalid provider dates before ranking rails and migrate legacy millisecond cache rows. - Add regression coverage for future timestamps, series date priority, and DB migration behavior. ## Validation - GitHub checks passed, including Unit Tests and Typechecks, Web E2E, Electron E2E on macOS/Ubuntu/Windows, CodeQL, builds, and Greptile Review.
38 lines
2.2 KiB
Markdown
38 lines
2.2 KiB
Markdown
# Date Handling
|
|
|
|
## Rules
|
|
|
|
- Use native `Date`, ISO strings, and epoch timestamps as the stored/runtime values.
|
|
- Use `date-fns` for parsing, arithmetic, and normalization logic.
|
|
- Use Angular `DatePipe` in templates when the value is already a `Date`, ISO string, or epoch timestamp.
|
|
- Use cached `Intl.DateTimeFormat` helpers in TypeScript-only formatting paths where Angular pipes are not available.
|
|
- Do not add new `moment` usage. The app no longer depends on it.
|
|
|
|
## Locale Strategy
|
|
|
|
- Date display should follow the user-selected app language from `TranslateService`.
|
|
- When a template renders localized month or weekday names, pass the normalized app locale explicitly to `DatePipe`.
|
|
- Angular locale data is registered in [apps/web/src/app/app-date-locales.ts](/apps/web/src/app/app-date-locales.ts).
|
|
- App language aliases are normalized in [libs/ui/pipes/src/lib/date-format.util.ts](/libs/ui/pipes/src/lib/date-format.util.ts):
|
|
- `ary` -> `ar-MA`
|
|
- `by` -> `be`
|
|
- `zhtw` -> `zh-Hant`
|
|
|
|
## Parsing Boundaries
|
|
|
|
- Normalize provider-specific or legacy date strings to ISO as early as possible.
|
|
- Keep optional epoch fields such as `startTimestamp` and `stopTimestamp` when the provider already supplies them.
|
|
- Avoid new non-standard `Date.parse(...)` usage for provider formats; prefer explicit `date-fns` parsing when the input is not ISO.
|
|
- Xtream `added` / `last_modified` values are provider-supplied epoch fields.
|
|
Normalize them through `toXtreamRecentlyAddedTimestamp()` /
|
|
`toXtreamRecentlyAddedEpochSeconds()` from `@iptvnator/shared/interfaces`
|
|
before ranking or storing recently-added content. Values more than 24 hours
|
|
in the future are treated as invalid so provider placeholders such as
|
|
`2030-01-01` cannot permanently pin the top of recently-added rails.
|
|
Recently-added ranking uses `added` before `last_modified` for live/VOD
|
|
content and `last_modified` before `added` for series. The VOD/live fallback
|
|
is intentional for providers that omit `added` but still expose a valid
|
|
`last_modified` epoch. Legacy cached millisecond epochs in `content.added`
|
|
are migrated to epoch seconds during database startup so indexed dashboard
|
|
queries can continue to compare and sort text timestamps directly.
|