GeoLeaf Core API - v3.19.0
    Preparing search index...
    • The conflicts kept for one layer, or for every layer.

      🛑 A STORE NOBODY CAN READ IS THE DEFECT, NOT THE FEATURE. local_images spent a month as a write-only store — images went in, its reader had been removed as "redundant", and a successful upload had nowhere to send the URL back to. The fiche records it. A conflict archive nothing can enumerate would be the same shape: the crushed version would be kept and unreachable, which is indistinguishable from not keeping it.

      ⚠️ Empty rather than throwing when the engine is not wired — a host asking "what did I crush?" on an application without the offline capability gets "nothing", which is true.

      ⚠️ Only the active profile's conflicts, unless asked otherwise. The store is shared by every profile of the origin, and a conflict belongs to the profile its write was queued under (profileId) — the same predicate as the queue's. A conflict without one, archived before 3.18.0, is listed under every profile.

      Parameters

      • OptionallayerId: string

        Restrict to this layer; omitted, every layer.

      • scope: { allProfiles?: boolean } = {}

        allProfiles: true lists every profile's conflicts.

      Returns Promise<ConflictRecord[]>

      The archived conflicts, newest write of each entity.

      const crushed = await GeoLeaf?.Storage?.listConflicts?.("sites");
      console.info(`${crushed?.length ?? 0} version(s) écrasée(s) conservée(s)`);