fix: export missing TimeRange type (#2590)

Bahtya · Bahtya · web-flow · commit 70e7286b6935 · 2026-04-10T17:39:19.000+08:00
* fix: export missing TimeRange type The TimeRange type is defined in shared/date/types.ts but was not re-exported from shared/index.ts, making it unavailable to consumers while the similar DateRange type is exported. Fixes #2589 Signed-off-by: bahtya <bahtyar153@qq.com> * fix: add TimeRange to date/index.ts re-export The shared/index.ts re-exports TimeRange from ./date, but TimeRange was missing from the date barrel (shared/date/index.ts). This caused a resolution failure. TimeRange is defined in shared/date/types.ts alongside DateRange and other date types, so it belongs in the same barrel export. Verified: build passes and TimeRange appears in dist/shared.d.ts. Bahtya --------- Signed-off-by: bahtya <bahtyar153@qq.com> Co-authored-by: Bahtya <bahtayr@gmail.com>
diff --git a/packages/core/src/shared/date/index.ts b/packages/core/src/shared/date/index.ts
@@ -35,6 +35,7 @@ export type {
   SegmentContentObj,
   SegmentPart,
   SegmentValueObj,
+  TimeRange,
   TimeSegmentObj,
   TimeSegmentPart,
 } from './types'
diff --git a/packages/core/src/shared/index.ts b/packages/core/src/shared/index.ts
@@ -2,7 +2,7 @@ export * from './arrays'
 export * from './browser'
 export * from './clamp'
 export { createContext } from './createContext'
-export { type DateRange, type DateStep, type DateValue, type SegmentPart, type TimeValue } from './date'
+export { type DateRange, type DateStep, type DateValue, type SegmentPart, type TimeRange, type TimeValue } from './date'
 export { getActiveElement } from './getActiveElement'
 export { handleAndDispatchCustomEvent } from './handleAndDispatchCustomEvent'
 export { isValidVNodeElement } from './isValidVNodeElement'
