{"version":"2.1.248","anchor":"peer-origin-conflicts-now-report-as-hook-conflicts","canonical_anchor":"peer-origin-conflicts-now-report-as-hook-conflicts","heading":"Peer-origin conflicts now report as hook conflicts","tier":"internal","area":"Cross-Session Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/peer-origin-conflicts-now-report-as-hook-conflicts","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Peer-origin conflicts now report as hook conflicts\n\nPeer-origin conflicts are labelled under the same cause as hook collisions.\n\n**What**\n\nConflicts originating from a peer are labelled with the same reason as hook collisions, so both show up under one cause instead of an unlabelled one.\n\n**Evidence**\n\n`return e === \"collision\" || e === \"peer\" ? \"hook\" : e;`\n\n- Area: Cross-Session Messaging\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}