{"version":"2.1.242","anchor":"directory-sync-explains-why-a-file-could-not-be-written-loca","canonical_anchor":"directory-sync-explains-why-a-file-could-not-be-written-loca","heading":"Directory sync explains why a file could not be written locally","tier":"notice","area":"Directory Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/directory-sync-explains-why-a-file-could-not-be-written-loca","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Directory sync explains why a file could not be written locally\n\nSync tells you why a pulled file could not be written, including case- or Unicode-only clashes.\n\n**What**\n\nFailures while writing pulled files into your working copy are now reported as refusals with a reason instead of thrown as raw errors, and the summary tells apart a genuine name clash from two files differing only by letter case or Unicode form, listing the paths involved.\n\n**Details**\n\n- Recognised reasons cover a missing anchor directory, a destination that refused the write, a file landing outside the sync root, a parent path escape, a parent that is not a directory, and a path that resolves outside the sync root.\n\n**Evidence**\n\n`WORKING_RESOLVES_OUTSIDE`\n\n- Area: Directory Sync\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}