Read a BCF project back into a map of clash-id -> [{ topicGuid, status }, ...].
Parses the machine-readable clash-ids: line that createBCFFromClashResult
embeds in each topic description. Topics without that line (e.g. the overflow
marker, or unrelated topics) are skipped.
A clash id can legitimately appear in more than one topic: element-mode
grouping (see groupClashes(result, { by: 'element' })) emits one group per
participating element, so a clash between two elements lands in two topics.
We therefore accumulate one entry per topic the id appears in rather than
overwriting, so no topic mapping is silently lost.
Read a BCF project back into a map of clash-id -> [{ topicGuid, status }, ...].
Parses the machine-readable
clash-ids:line thatcreateBCFFromClashResultembeds in each topic description. Topics without that line (e.g. the overflow marker, or unrelated topics) are skipped.A clash id can legitimately appear in more than one topic: element-mode grouping (see
groupClashes(result, { by: 'element' })) emits one group per participating element, so a clash between two elements lands in two topics. We therefore accumulate one entry per topic the id appears in rather than overwriting, so no topic mapping is silently lost.