Member Junction
    Preparing search index...
    • The rail key a contribution asked to lead on for an UNSAVED record, or null.

      Sits beside ShouldPersistChromeActiveGroup because it answers the other half of the same question: that one says a new record must not restore a stored position, this one says where it should go instead. Without it a new record opens on the lead group, which is usually a summary -- and a summary of a record with no data is a page of blanks to look past.

      Highest Priority wins when several contributions on one entity declare it, matching how every other conflict between registrations is settled. Null when none does, which leaves the existing behaviour exactly as it was -- this is opt-in per form, not a change to the default.

      Pure so it can be tested without standing up a container: the caller supplies the registrations and the key-derivation it already uses for the rail.

      Type Parameters

      • TMeta extends { entity?: string; leadsWhenUnsaved?: boolean }

      Parameters

      • entityName: string | null | undefined
      • registrations: readonly { Metadata?: TMeta; Priority?: number }[]
      • railKeyOf: (meta: TMeta) => string | null

      Returns string | null