{"version":"2.1.251","anchor":"clearer-error-when-a-working-directory-path-is-invalid","canonical_anchor":"clearer-error-when-a-working-directory-path-is-invalid","heading":"Clearer error when a working directory path is invalid","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/clearer-error-when-a-working-directory-path-is-invalid","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Clearer error when a working directory path is invalid\n\nAdding a working directory now says whether the path is unresolvable, missing or malformed.\n\n**What**\n\nAdding a working directory now separates a path that cannot be resolved at all from one that simply does not exist, and calls out paths containing a null character with their own message.\n\n**Details**\n\n- New invalid-path outcome alongside the existing not-found outcome.\n- Null-byte paths are reported as unusable as a working directory rather than as missing.\n\n**Evidence**\n\n`contains a null character, so it can't be used as a working directory`\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}