@buzzr/dfs-engine
    Preparing search index...

    Function matchGameLogEntry

    • Pick the gamelog entry that best matches a leg's bet date. ±36h window. Returns null when nothing matches; on ambiguity returns the forward-biased closest.

      When to use this vs findGameLogCandidates:

      • findGameLogCandidates returns [] / [a] / [a, b] so callers can detect doubleheader ambiguity and defer to a picker. Use this in settlement watchers / cron jobs.
      • matchGameLogEntry (this fn) collapses ambiguity by picking the closest forward-biased candidate. Use in UI verification flows or tests where "give me a single answer" is OK.

      Type Parameters

      Parameters

      • legGameDateHint: string | null
      • entries: T[]
      • opts: { assumeFirst?: boolean; window?: number } = {}

      Returns T | null